Events on SQL Server

Hi,
We had a problem on one of our SQL Servers, basically it stopped accepting
connections and we could not even connect to it with the Enterprise Manager.
At the same time we started getting a lot of the following events
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 5/2/2005
Time: 2:58:56 AM
User: N/A
Computer: SQLSERVER
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: 17120,
SQL Server could not spawn process_loginread thread.
.
Data:
0000: e0 42 00 00 10 00 00 00 àB.....
0008: 0a 00 00 00 53 00 51 00 ...S.Q.
0010: 4c 00 53 00 45 00 52 00 L.S.E.R.
0018: 56 00 45 00 52 00 00 00 V.E.R...
0020: 00 00 00 00 ...
----
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 5/2/2005
Time: 2:51:15 AM
User: N/A
Computer: SQLSERVER
Description:
The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: Error:
17803, Severity: 20, State: 12
Insufficient memory available..
Data:
0000: 8b 45 00 00 14 00 00 00 <E.....
0008: 0a 00 00 00 53 00 51 00 ...S.Q.
0010: 4c 00 53 00 45 00 52 00 L.S.E.R.
0018: 56 00 45 00 52 00 00 00 V.E.R...
0020: 11 00 00 00 4a 00 6f 00 ...J.o.
0028: 75 00 72 00 6e 00 61 00 u.r.n.a.
0030: 6c 00 69 00 6e 00 67 00 l.i.n.g.
0038: 5f 00 4a 00 61 00 6e 00 _.J.a.n.
0040: 30 00 35 00 00 00 0.5...
At the same time SQL was using 1.9Gb ov Ram & an other 1.9 VM. Server has
4Gb physical mem available though. We had to restart the services to bring
it up again..
ANy insight appreciated
Thanks NichYou may want to apply
http://support.microsoft.com/default.aspx?scid=kb;en-us;893312 to try and
resolve SQL memory problems, but if they persist contact Microsoft Product
Support for assistance.
Adrian
"Nicholas Aquilina" <nickaquilina@.hotmail.com> wrote in message
news:%23kItF8MUFHA.2172@.tk2msftngp13.phx.gbl...
> Hi,
> We had a problem on one of our SQL Servers, basically it stopped accepting
> connections and we could not even connect to it with the Enterprise
> Manager.
> At the same time we started getting a lot of the following events
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 5/2/2005
> Time: 2:58:56 AM
> User: N/A
> Computer: SQLSERVER
> Description:
> The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be
> found. The local computer may not have the necessary registry information
> or message DLL files to display messages from a remote computer. You may
> be able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> 17120, SQL Server could not spawn process_loginread thread.
> .
> Data:
> 0000: e0 42 00 00 10 00 00 00 àB.....
> 0008: 0a 00 00 00 53 00 51 00 ...S.Q.
> 0010: 4c 00 53 00 45 00 52 00 L.S.E.R.
> 0018: 56 00 45 00 52 00 00 00 V.E.R...
> 0020: 00 00 00 00 ...
> ----
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 5/2/2005
> Time: 2:51:15 AM
> User: N/A
> Computer: SQLSERVER
> Description:
> The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be
> found. The local computer may not have the necessary registry information
> or message DLL files to display messages from a remote computer. You may
> be able to use the /AUXSOURCE= flag to retrieve this description; see Help
> and Support for details. The following information is part of the event:
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available..
> Data:
> 0000: 8b 45 00 00 14 00 00 00 <E.....
> 0008: 0a 00 00 00 53 00 51 00 ...S.Q.
> 0010: 4c 00 53 00 45 00 52 00 L.S.E.R.
> 0018: 56 00 45 00 52 00 00 00 V.E.R...
> 0020: 11 00 00 00 4a 00 6f 00 ...J.o.
> 0028: 75 00 72 00 6e 00 61 00 u.r.n.a.
> 0030: 6c 00 69 00 6e 00 67 00 l.i.n.g.
> 0038: 5f 00 4a 00 61 00 6e 00 _.J.a.n.
> 0040: 30 00 35 00 00 00 0.5...
>
> At the same time SQL was using 1.9Gb ov Ram & an other 1.9 VM. Server has
> 4Gb physical mem available though. We had to restart the services to bring
> it up again..
> ANy insight appreciated
> Thanks Nich
>