Error 17827 from SQL Server 2005 Express Edition

Hi,
I'm using SQL server 2005 Express Edition in my solution and I've run into a
problem that I can't find any information about.
The application was running OK (for several days) until this happend just
out of the blue.
The application is written in C++ and we are using ADO to access the
database.
The authentication used with sql server user names and passwords.
I have not changed the password for any user
In the SQL server error log I found the following lines.
2007-03-15 01:34:01.13 Server Server resumed execution after being idle
209 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 02:34:01.61 Server Server resumed execution after being idle
213 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:00.78 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
2007-03-15 03:11:00.80 Server The current event was not reported to the
Windows Events log. Operating system error = 5(error not found). You may nee
d
to clear the Windows Events log if it is full.
2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:02.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:05.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:11.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:23.45 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:48.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:12:38.31 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:14:16.67 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:15:55.91 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:17:35.19 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
Does anyone have any ideas why i get this behavior from SQL?
After we rebooted the system everything worked OK again.
Voja TadicVoja,
How many connections are being made to your SQL Express instance? Although
there is no hard limit to connections, there are resource limits on memory
and once those are used up, you will have problems.
Might you have many connections that should have closed during the several
successful days, but have not? If so, you many have many unused connections
still consuming resources.
The reason I ask is because the only instance of 17827 I see in technet is
SQL Server 2000 extended stored procedure related and means: The maximum
number of '%1!ld!' remote connections is currently in use.
Although that is not directly your error, it may be a hint as to the
underlying problem.
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
> Hi,
> I'm using SQL server 2005 Express Edition in my solution and I've run into
> a
> problem that I can't find any information about.
> The application was running OK (for several days) until this happend just
> out of the blue.
> The application is written in C++ and we are using ADO to access the
> database.
> The authentication used with sql server user names and passwords.
> I have not changed the password for any user
>
> In the SQL server error log I found the following lines.
>
> 2007-03-15 01:34:01.13 Server Server resumed execution after being
> idle
> 209 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 02:34:01.61 Server Server resumed execution after being
> idle
> 213 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:00.78 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
> 2007-03-15 03:11:00.80 Server The current event was not reported to
> the
> Windows Events log. Operating system error = 5(error not found). You may
> need
> to clear the Windows Events log if it is full.
> 2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:02.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:05.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:11.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:23.45 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:48.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:12:38.31 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:14:16.67 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:15:55.91 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:17:35.19 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
>
> Does anyone have any ideas why i get this behavior from SQL?
>
> After we rebooted the system everything worked OK again.
> Voja Tadic|||Hi,
I only use one connection for this application and I'm closing the
connection after each action to the database. I'm also using the connection
pooling functionality in ADO. This application uses the database alot.
I do have one additional application that uses ADO.DET and connects,
retrives data and dissconects and then terminats. This is done ~20-30 times
each day.
"Russell Fields" wrote:

> Voja,
> How many connections are being made to your SQL Express instance? Althoug
h
> there is no hard limit to connections, there are resource limits on memory
> and once those are used up, you will have problems.
> Might you have many connections that should have closed during the several
> successful days, but have not? If so, you many have many unused connectio
ns
> still consuming resources.
> The reason I ask is because the only instance of 17827 I see in technet i
s
> SQL Server 2000 extended stored procedure related and means: The maximum
> number of '%1!ld!' remote connections is currently in use.
> Although that is not directly your error, it may be a hint as to the
> underlying problem.
> RLF
> "vojat" <vojat@.discussions.microsoft.com> wrote in message
> news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
>
>|||Voja,
I don't have any real good insight for you. You might look here for the
answer or someone to talk with:
http://blogs.msdn.com/sql_protocols.../23/558651.aspx
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0ACE3553-246E-46EC-936D-5A57E1181A02@.microsoft.com...[vbcol=seagreen]
> Hi,
> I only use one connection for this application and I'm closing the
> connection after each action to the database. I'm also using the
> connection
> pooling functionality in ADO. This application uses the database alot.
> I do have one additional application that uses ADO.DET and connects,
> retrives data and dissconects and then terminats. This is done ~20-30
> times
> each day.
>
> "Russell Fields" wrote:
>