Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2005 Forums  SQL Server Administration (2005)  Multiple Non-Yielding Schedulers

Author  Topic  lilsamp Starting Member 3 Posts Posted - 2012-02-23 : 19:25:29 I'm running SQL Server 2005 SP2 Enterprise Edition, Windows 2003 x64. Today, I had a non-yielding session on the scheduler. This has happened previously and I was planning on recycling the SQL Service tonight. A couple of hours later, I got another non-yielding session on another scheduler. That’s the first time I have seen two non-yielding schedulers on different physical sockets. Seconds after the non-yielding session on another scheduler occurred, I started to get failures connecting to the SQL Server instance. I started receiving weird errors like “The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server.” My question is did the SQLOS have a problem dealing with multiple non-yielding schedulers? It seems kind of weird that 30 secs after the failure, I started experiencing connection issues. Thoughts?