Help - Corrupted SQL Server 2K Log. Is this serious

[Covi]

Hello,

I have a SS2K (SP3) that is appending very wierd looking error messages
to the SQL Server Log (Current). The messages are not formatted as
other log entries. The messages suggest some kinda dump information.
The messages have the following characteristics:

Date Information is invalid
Source information is invalid
Message information is strange

The following is a message that appear in my current SQL Server Log
DATE:78008454
SOURCE: Module(MSVCRT+
Message (_endthread+000000C1)


There are many messages like this in the log.

Is this serious?

Thanks - Covi

[Erland Sommarskog]

Covi (co****@earthlink.net) writes:

I have a SS2K (SP3) that is appending very wierd looking error messages
to the SQL Server Log (Current). The messages are not formatted as
other log entries. The messages suggest some kinda dump information.
The messages have the following characteristics:

Date Information is invalid
Source information is invalid
Message information is strange

The following is a message that appear in my current SQL Server Log
DATE:78008454
SOURCE: Module(MSVCRT+
Message (_endthread+000000C1)

There are many messages like this in the log.

Is this serious?

When a connection runs into an execution error, one that really should
not occur, for instance an access violation, SQL Server terminates the
connection and leaves a stack dump in the error log. Most such dumps
are due to bugs in SQL Server, and could come from specific queries.
Hardware errors could be involved too. In the latter case, there is
certainly cause for alarm. If you want to sleep better at night, you
could run a DBCC CHECKDB on the database related to the dumps.

But stackdumps can occur on healthy machines too.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp