| Groups | Blog | Home |
sql server connect : Error 17827 from SQL Server 2005 Express Edition
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 [quoted text, click to view] "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'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.
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. [quoted text, click to view] "Russell Fields" wrote:
> 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@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 > >
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/archive/2006/03/23/558651.aspx RLF [quoted text, click to view] "vojat" <vojat@discussions.microsoft.com> wrote in message news:0ACE3553-246E-46EC-936D-5A57E1181A02@microsoft.com... > 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? >> 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 >> >> >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |