Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: SQL Server cluster resource fails to come online until the cluster service is restarted


BUG #:236421 (SHILOH_BUGS)

↑ Back to the top


Symptoms

If the SQL Server cluster resource is in an "online pending" state and the cluster service sends a termination request to the resource, the resource may not successfully come online again on the node until the cluster service is restarted.

The cluster service usually sends a termination request to a resource to perform a failover.

↑ Back to the top


Cause

When the cluster resource DLL terminates a resource that is in the "online pending" state, it does not communicate this information to the cluster service correctly. This puts the cluster service in an unknown state and prevents this resource from coming back online.

↑ Back to the top


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

↑ Back to the top


Workaround

Restart the cluster service on the node.

↑ Back to the top


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.

↑ Back to the top


More Information

Steps to Reproduce Behavior

  1. Configure the SQL Server resource so that it cannot connect successfully; for instance, configure it to use a port that is already in use.
  2. Start the SQL Server resource so that it remains in an "online pending" state.
  3. Perform a failover to another node.
  4. Fail the SQL Server group back to the original node.
  5. The cluster will fail repeatedly until the cluster service is restarted.

↑ Back to the top


Keywords: kbsql2005clustersweep, kbbetapublic, kbbug, kbfix, kbsqlserv2000sp1fix, sql2ksp1fix, kb

↑ Back to the top

Article Info
Article ID : 300183
Revision : 3
Created on : 4/20/2018
Published on : 4/20/2018
Exists online : False
Views : 176