FIX: Error messages from the SQL Server resource DLL may not be logged in the Application log in the Event Viewer

Article translations Article translations
Article ID: 290128 - View products that this article applies to.
This article was previously published under Q290128
BUG#: 235040 (Shiloh_bugs)
Expand all | Collapse all

SYMPTOMS

After a failover and failback of the SQL Server resource group, error messages from the SQL Server resource DLL may not be logged in the Application Log in the Event Viewer. The following two error messages are examples of messages that may not be logged:
Event Type: Error
Event Source: MSSQLSERVER
Event ID: 17052
Description: [sqsrvres] CheckServiceAlive: Service is dead

Event Type: Error
Event Source: MSSQLSERVER
Event ID: 17052
Description: [sqsrvres] OnlineThread: service stopped while waiting for QP.
Although these messages may not be logged to the Event Viewer, they are still also logged, by default, to the cluster log (%systemroot%\Cluster\cluster.log) on that node.

RESOLUTION

To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

If you restart the cluster service, logging in the Event Viewer should resume.

STATUS

Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

Properties

Article ID: 290128 - Last Review: March 14, 2006 - Revision: 4.2
APPLIES TO
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Developer Edition
Keywords: 
kbqfe kbbug kbfix kbsqlserv2000sp1fix KB290128

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com