May 11, 2010 at 9:02 pm
Hi,
I am seeing this error message in our one of the sql server 2005 machine
"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"
Can anyone help me to find out the rootcause and how to resolve this issue ?
Thanks in Advance.
May 11, 2010 at 11:17 pm
Did you
Check the SQL Server error log and the Windows event logs for information about possible related problems"
???
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
May 12, 2010 at 12:24 am
Henrico Bekker (5/11/2010)
Did youCheck the SQL Server error log and the Windows event logs for information about possible related problems"
???
1) SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL\Data\XXXX.mdf] in database
[QDB] (8). The OS file handle is 0x000008F4. The offset of the latest long I/O is: 0x000001e1126000.
2) AppDomain 57 (XXXX.dbo[runtime].62) is marked for unload due to memory pressure.AppDomain 57 (XXXX.dbo[runtime].62) unloaded.
3) 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. [CLIENT: XXX.XX.X.XX].
These are the error messages available in the sql server error log file.
May 12, 2010 at 5:40 am
Any update on this ?
May 13, 2010 at 2:48 am
1) SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\MSSQL\Data\XXXX.mdf] in database
----------------------------------------
I had this when before my disk failed. check what else is running on the system at the same time - any I/O intensive operations may cause this but it is most likely a disk problem.
2) AppDomain 57 (XXXX.dbo[runtime].62) is marked for unload due to memory pressure.AppDomain 57 (XXXX.dbo[runtime].62) unloaded.
-----------------------------------------
Had this when a CLR was hitting memory pressure. this may not be the same problem (it may not ba a problem at all), but I had to increase the size of MEMTOLEAVE after repeated CLR fails.
3) 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
------------------------------------------
Not so sure about this one - was it associated with the others?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply