SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection.

Hello,

I have a SQL 2008 R2 X64 server, it is running a process engine application framework called Metastorm BPM.

Around 1AM this error occurred as well as we could not RDP into the server with an error of Local Security Authority could not be contacted. The server was restarted and we received the second error below which is filling up the log.

Any ideas why?


Log Name:      Application
Source:        Metastorm Process Engine
Date:          9/12/2011 12:56:14 AM
Event ID:      46
Task Category: eServerConfigurer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computer
Description:
KeepAlive update failed for this engine.  Engine name: PHXSQLDB$computer.  Operation: opening database connection.  ErrorCode:-2147467259  Description:'[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.'  Source:Microsoft OLE DB Provider for SQL Server  SQL State:08001  NativeErrorCode: 11
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Metastorm Process Engine" />
    <EventID Qualifiers="57869">46</EventID>
    <Level>2</Level>
    <Task>13</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-12T04:56:14.000000000Z" />
    <EventRecordID>54635</EventRecordID>
    <Channel>Application</Channel>
    <Computer>computer</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PHXSQLDB$computer</Data>
    <Data>opening database connection</Data>
    <Data>ErrorCode:-2147467259  Description:'[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.'  Source:Microsoft OLE DB Provider for SQL Server  SQL State:08001  NativeErrorCode: 11</Data>
  </EventData>
</Event>

We rebooted the server and we could log in and the application is running fine but the logs are filling up with this error.


Log Name:      Application
Source:        MSSQLSERVER
Date:          9/12/2011 6:38:05 AM
Event ID:      17189
Task Category: Logon
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     computer
Description:
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: 172.16.30.50]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSSQLSERVER" />
    <EventID Qualifiers="49152">17189</EventID>
    <Level>2</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-12T10:38:05.000000000Z" />
    <EventRecordID>54725</EventRecordID>
    <Channel>Application</Channel>
    <Computer>computer</Computer>
    <Security />
  </System>
  <EventData>
    <Data>c0000000</Data>
    <Data> [CLIENT: 172.16.30.50]</Data>
    <Binary>254300001000000009000000500048005800530051004C0044004200000000000000</Binary>
  </EventData>
</Event>
LVL 1
hoffmanconsultingllcAsked:
Who is Participating?
 
hoffmanconsultingllcAuthor Commented:
That does not explain why the system would receive these errors. I have also noticed that CPU utilization jumped to about 60% and memory utilization went above the amount of memory installed in the server which is 8GB.

0
All Courses

From novice to tech pro — start learning today.