BUG: The Setup program of SQL Server 2000 Service Pack 2 or a later version may stop responding in a Windows clustering environment if there is an offline database (320524)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions) SP3a
  • Microsoft SQL Server 2000 (all editions) SP3
  • Microsoft SQL Server 2000 Enterprise Edition SP2

This article was previously published under Q320524
BUG #: 356934, 356933 (SHILOH_BUGS)

SYMPTOMS

When you upgrade a virtual instance of Microsoft SQL Server 2000 to SQL Server 2000 Service Pack 2 (SP2) or a later version in a Windows Clustering environment, and one or more databases in your instance of SQL Server are offline, the Setup program may stop responding, and you may receive the following error message:
An error occurred while creating virtual server resources for clustering. Cannot create a file when that file already exists.
Additionally, detailed error messages are logged in the Setup log files (Sqlsp.log and Sqlclstr.log). These files are located in the Windows installation folder.

The Sqlsp.log file indicates that CreateVirtualServerResources returned error 183:
20:22:25 Begin Action : CreateVirtualServerResources
20:22:25 Begin: BeforeFTS()
20:22:25 Begin Action : EnumerateNodes
20:22:25 End Action : EnumerateNodes
20:22:25 End: AfterFTS()
20:22:35 End Action : CreateVirtualServerResources
20:22:35 CreateVirtualServerResources returned: 183
20:28:38 Begin Action : ClusterErrorCleanup
The Sqlclstr.log file indicates that the cause of the failure is the offline database. In this sample log file, the pubs database is indicated as the offline database:
about to open cluster
calling ClusterGetComputerNames
ClusterGetComputerNames: m_LocalComputerName=[]
ClusterGetComputerNames: calling GetComputerName
ClusterGetComputerNames: m_LocalComputerName=[GXPRO]
ClusterGetComputerNames: calling ClusterOpenEnum
ClusterGetComputerNames: calling ClusterEnum[0]
ClusterGetComputerNames: calling ClusterEnum[1]
called ClusterGetComputerNames, status=0x0
cConnectString="ODBC;DSN='';DRIVER={SQL Server};SERVER=VSQL;DATABASE=master;Trusted_Connection=yes"
Database 'pubs' cannot be opened because it is offline.

[sqlclusterSetup.cpp:1295] : 183 (0xb7): ~~~ DoClusterSetupWork
Note In the Japanese version of SQL Server 2000 Enterprise Edition SP2, unlike the English version, the Sqlclstr.log file does not include an error message that refers to the offline database. This is the cause of the failure.

CAUSE

This problem occurs because Setup program cannot access the database.

During installation in a Windows Clustering environment, Setup program must query the user databases to make sure that all the database files are on disk resources that have the correct dependencies and the virtual SQL Server resource. The virtual SQL Server resource is required for the failover support. When a database is offline, Setup program cannot access the database.

WORKAROUND

To work around this problem, bring the inaccessible database online, and then rerun the service pack Setup program.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

You do not experience this problem during SQL Server SP1 Setup. During the setup of SQL Server SP2 or a later version, you receive the following error message:
Setup has detected one or more databases and filegroups which are not writable. Refer to sp2readme.htm for more information. Setup will continue.
Then, you can continue the setup of the service pack. If you choose to continue, the Setup program stops responding later (as explained in the "Symptoms" section). However, in the Setup program for SQL Server SP1, you cannot continue the Setup program (nor are you given the option to continue).

REFERENCES

A database may go offline and become inaccessible for various reasons. For more information about how to bring the database back online, see the following topics in SQL Server Books Online:
  • "Loading"
  • "Recovering"
  • "Suspect"

Modification Type:MajorLast Reviewed:9/2/2004
Keywords:kbsetup kbUpgrade kbClustering kbtshoot kbbug kbpending KB320524 kbAudDeveloper