RBh


SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.

server is 64 bit, Windows 2003 R2 SP2

SQL server is MS SQL Server 2005 without any Service pack

Any ideas guys

Server stopped responding to the queries so after waiting for a while we had to reboot the machine. Now it is fine but can get the error again any time.

Thanks



Re: SQL server 2005- hanging problem

GlennAlanBerry


Are there any other errors in the Windows System or Application Event logs Are there any errors in the SQL Error logs

If you are still on SQL Server 2005 RTM (Build 1399), you really should think about getting SP2 installed. There are a lot of fixes and enhancements in SP2.






Re: SQL server 2005- hanging problem

RBh

Thanks for your response.

Application logs have the same error as the sql server error log.

Source Logon

Message
Error: 17189, Severity: 16, State: 1.

Source Logon

Message
SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.

System log has no error during that time.

I checked other sites all says error is fixed in windows server 2003 sp2 but we already have windows server 2003 SP2.

We are still on the original build, SP 2 for sql server 2005 doesn't say anything about fixing these type of issues.






Re: SQL server 2005- hanging problem

GlennAlanBerry

Are there any SQL Server minidump files in the SQL Server Log directory If so, you would want to get those minidumps to Microsoft PSS.

I also strongly recommend that you install SQL Server 2005 SP2, since it fixes lots of other known issues. You may get lucky, and it will help with this issue.





Re: SQL server 2005- hanging problem

Ron D.

If no dump was generated in SQL Server Log directory, either restart you server with -y17189 or issue dbcc traceon (17189,1) and a dump will be generated when this reoccurs.

Thanks, Ron D.