Failed Assertion Logmgr.cpp -- help!

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/1/2004
Time: 9:19:23 PM
User: HENT\Administrator
Computer: HESV0105
Description:
17066 :
SQL Server Assertion: File: <"logmgr.cpp">, line=2637
Failed Assertion = '!freeLC->lc_flushed'.
Data:
0000: aa 42 00 00 10 00 00 00 aB.....
0008: 09 00 00 00 48 00 45 00 ...H.E.
0010: 53 00 56 00 30 00 31 00 S.V.0.1.
0018: 30 00 35 00 00 00 0f 00 0.5....
0020: 00 00 49 00 4e 00 53 00 ..I.N.S.
0028: 49 00 47 00 48 00 54 00 I.G.H.T.
0030: 5f 00 44 00 42 00 5f 00 _.D.B._.
0038: 56 00 33 00 32 00 00 00 V.3.2...
We are running SQL 2000 SP3 on Windows 2000 Server SP4. The server is NOT a
domain controller. During the time of the error, there were no database
maintenance plans scheduled to run. Veritas BackUp exec is running on
another server, but it is done with SQL by 6:00pm, the error always happens
after that. There are no DTS packages running, either
This error happens occasionally, roughly 2-3 times per month. When it
happens, SQL maxes out processor utilization and eats up the pagefile.
Server is unresponsive, and the only course of action is to reboot the
server.
I've looked everywhere, support.microsoft.com, www.experts-exchange.com,
google, and many many newsgroups. Has anyone encountered this?
The database it fails on changes, this time it was HP Insight Manager, last
time it was our PACE replica database.Hi Kevin,
Your best bet is goign to be to contact Microsoft CSS - they can help you ge
t to the bottom of this.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine
"Kevin Anderson" <Kevin Anderson@.discussions.microsoft.com> wrote in message
news:700E664C-667C-4C82-A08E-81E8647598F9@.microsoft.com...
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/1/2004
Time: 9:19:23 PM
User: HENT\Administrator
Computer: HESV0105
Description:
17066 :
SQL Server Assertion: File: <"logmgr.cpp">, line=2637
Failed Assertion = '!freeLC->lc_flushed'.
Data:
0000: aa 42 00 00 10 00 00 00 aB.....
0008: 09 00 00 00 48 00 45 00 ...H.E.
0010: 53 00 56 00 30 00 31 00 S.V.0.1.
0018: 30 00 35 00 00 00 0f 00 0.5....
0020: 00 00 49 00 4e 00 53 00 ..I.N.S.
0028: 49 00 47 00 48 00 54 00 I.G.H.T.
0030: 5f 00 44 00 42 00 5f 00 _.D.B._.
0038: 56 00 33 00 32 00 00 00 V.3.2...
We are running SQL 2000 SP3 on Windows 2000 Server SP4. The server is NOT a
domain controller. During the time of the error, there were no database
maintenance plans scheduled to run. Veritas BackUp exec is running on
another server, but it is done with SQL by 6:00pm, the error always happens
after that. There are no DTS packages running, either
This error happens occasionally, roughly 2-3 times per month. When it
happens, SQL maxes out processor utilization and eats up the pagefile.
Server is unresponsive, and the only course of action is to reboot the
server.
I've looked everywhere, support.microsoft.com, www.experts-exchange.com,
google, and many many newsgroups. Has anyone encountered this?
The database it fails on changes, this time it was HP Insight Manager, last
time it was our PACE replica database.