November 9, 2016 at 8:45 pm
I am getting a error message
Event Type:Error
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:17187
Date:11/10/2016
Time:10:54:59 AM
User:N/A
Computer:TSERVER
Description:
SQL Server is not ready to accept new client connections.
Wait a few minutes before trying again.
If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 23 43 00 00 10 00 00 00 #C......
0008: 08 00 00 00 54 00 53 00 ....T.S.
0010: 45 00 52 00 56 00 45 00 E.R.V.E.
0018: 52 00 00 00 00 00 00 00 R.......
and then my entire server hangs (cannot log-in, or do anything), we are have 2 client software using SQL Server,1 of the software works just fine, but the other one just hangs.
But after force restart of the server, everything works ok.
November 9, 2016 at 9:48 pm
s0da9 (11/9/2016)
I am getting a error messageEvent Type:Error
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:17187
Date:11/10/2016
Time:10:54:59 AM
User:N/A
Computer:TSERVER
Description:
SQL Server is not ready to accept new client connections.
Wait a few minutes before trying again.
If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 23 43 00 00 10 00 00 00 #C......
0008: 08 00 00 00 54 00 53 00 ....T.S.
0010: 45 00 52 00 56 00 45 00 E.R.V.E.
0018: 52 00 00 00 00 00 00 00 R.......
and then my entire server hangs (cannot log-in, or do anything), we are have 2 client software using SQL Server,1 of the software works just fine, but the other one just hangs.
But after force restart of the server, everything works ok.
What is the output of this query on the troubled server?
😎
SELECT @@VERSION;
November 10, 2016 at 1:16 am
Can you check the server's error log? By default it is configured to write into the error log details about failed logins. You'll be able to see there the reason that the login failed. Another thing that I'll check is if someone changed the configuration option "user connections" and limited the number of connections that the server can have (but I have to admit that it is a guess by my side).
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
November 13, 2016 at 6:01 pm
Eirikur Eiriksson (11/9/2016)
s0da9 (11/9/2016)
I am getting a error messageEvent Type:Error
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:17187
Date:11/10/2016
Time:10:54:59 AM
User:N/A
Computer:TSERVER
Description:
SQL Server is not ready to accept new client connections.
Wait a few minutes before trying again.
If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 23 43 00 00 10 00 00 00 #C......
0008: 08 00 00 00 54 00 53 00 ....T.S.
0010: 45 00 52 00 56 00 45 00 E.R.V.E.
0018: 52 00 00 00 00 00 00 00 R.......
and then my entire server hangs (cannot log-in, or do anything), we are have 2 client software using SQL Server,1 of the software works just fine, but the other one just hangs.
But after force restart of the server, everything works ok.
What is the output of this query on the troubled server?
😎
SELECT @@VERSION;
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86) Jul 9 2008 14:43:34 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)
November 13, 2016 at 6:07 pm
Adi Cohn-120898 (11/10/2016)
Can you check the server's error log? By default it is configured to write into the error log details about failed logins. You'll be able to see there the reason that the login failed. Another thing that I'll check is if someone changed the configuration option "user connections" and limited the number of connections that the server can have (but I have to admit that it is a guess by my side).Adi
here the reason for the failed log-ins. the only different was the CLIENT
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 10.0.0.44]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
November 13, 2016 at 7:29 pm
s0da9 (11/13/2016)
Adi Cohn-120898 (11/10/2016)
Can you check the server's error log? By default it is configured to write into the error log details about failed logins. You'll be able to see there the reason that the login failed. Another thing that I'll check is if someone changed the configuration option "user connections" and limited the number of connections that the server can have (but I have to admit that it is a guess by my side).Adi
here the reason for the failed log-ins. the only different was the CLIENT
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 10.0.0.44]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.%5B/quote%5D
The error is telling you the problem. It's saying the server is configured for Windows authentication only. If you also want to accept connections using SQL Server logins, you have to run in Mixed Mode.
November 13, 2016 at 10:38 pm
s0da9 (11/13/2016)
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86) Jul 9 2008 14:43:34 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)
Strongly suggest you update this SQL Server instance (Microsoft SQL Server 2008 Service Pack 4 (SP4)).
😎
November 14, 2016 at 5:28 pm
Ed Wagner (11/13/2016)
s0da9 (11/13/2016)
Adi Cohn-120898 (11/10/2016)
Can you check the server's error log? By default it is configured to write into the error log details about failed logins. You'll be able to see there the reason that the login failed. Another thing that I'll check is if someone changed the configuration option "user connections" and limited the number of connections that the server can have (but I have to admit that it is a guess by my side).Adi
here the reason for the failed log-ins. the only different was the CLIENT
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 10.0.0.44]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.%5B/quote%5D
The error is telling you the problem. It's saying the server is configured for Windows authentication only. If you also want to accept connections using SQL Server logins, you have to run in Mixed Mode.
Hi, I am sorry for asking but how do I do that?
November 15, 2016 at 1:54 am
s0da9 (11/14/2016)
Ed Wagner (11/13/2016)
s0da9 (11/13/2016)
Adi Cohn-120898 (11/10/2016)
Can you check the server's error log? By default it is configured to write into the error log details about failed logins. You'll be able to see there the reason that the login failed. Another thing that I'll check is if someone changed the configuration option "user connections" and limited the number of connections that the server can have (but I have to admit that it is a guess by my side).Adi
here the reason for the failed log-ins. the only different was the CLIENT
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: 10.0.0.44]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.%5B/quote%5D
The error is telling you the problem. It's saying the server is configured for Windows authentication only. If you also want to accept connections using SQL Server logins, you have to run in Mixed Mode.
Hi, I am sorry for asking but how do I do that?
Right click on the SQL Server Instance in SSMS, select Properties->Security and tick the "Sql Server and Windows Authentication mode" option.
😎
Alternatively you can change the Registry setting directly (check the path on your instance):
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer -> LoginMode = 2
November 17, 2016 at 3:29 am
This was removed by the editor as SPAM
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply