Re: Error 17827 from SQL Server 2005 Express Edition

Voja,

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@xxxxxxxxxxxxxxxx
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


.

Relevant Pages

  • Re: connect to named instance w/ non-default port
    ... SQL Native Client Configuration. ... An error has occurred while establishing a connection to the server. ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.sqlserver.connect)
  • Re: How to enable Analysis Services with IIS on Win 2K
    ... Assuming that there is no firewall involved I don't see why not. ... >> Can you bring that up though the Intenet connection? ... >> SQL BI Product Unit ... >>> client machine, connected through the Internet, located outside the ...
    (microsoft.public.sqlserver.olap)
  • Re: Concurrent database access in SQL 2005 Mobile
    ... Please stick to having an "dummy" connection in Open State. ... SQL CE/Mobile has a background thread that flushes the changes ... they run for long hours and we have not seen memory leaks so far. ... then opens his work forms and it's in ...
    (microsoft.public.sqlserver.ce)
  • Re: Concurrent database access in SQL 2005 Mobile
    ... Please stick to having an "dummy" connection in Open State. ... So it is a kind of asynchronous commit which happens every 10 ... I am not sure of this claim as we have many applications built on SQL CE ... then opens his work forms and it's in ...
    (microsoft.public.sqlserver.ce)
  • Re: SQL Server 2000 / 2005 Encryption
    ... encrypting the connection makes sense to me. ... This is possible on SQL 2005 via built-in T-SQL statements and functions, but requires 3rd-party tools, usually some sort of extended procedures. ... to encrypt your SSL connections will be different. ... Excel does not know how to decrypt data stored in SQL Server 2005 in encrypted form. ...
    (microsoft.public.sqlserver.security)
Quantcast