Microsoft KB Archive/300919

= FIX: SQL Server 2000 Service Pack 1 Setup May Fail when Applied to a Server with Non-writable Databases =

Article ID: 300919

Article Last Modified on 10/15/2002

-

APPLIES TO


 * Microsoft SQL Server 2000 Service Pack 1

-



This article was previously published under Q300919



BUG #: 353868 (SHILOH_BUGS)



SYMPTOMS
The SQL Server 2000 Service Pack 1 (SP1) setup may fail with the following error message if any of the databases on the server on which the service pack is installed, are in a non-writable state:

In order to begin an upgrade, databases and filegroups must be writable and you must have permission to access the databases. Correct the problem and restart the setup.

A database is considered to be in a non-writable state if the database status is:
 * SUSPECT
 * RECOVERING
 * OFFLINE
 * EMERGENCY MODE
 * READ-ONLY
 * LOADING

The error message may also occur on servers that are configured to participate in log shipping as standby servers. Because the secondary databases are either in LOADING or READ-ONLY state, the service pack setup fails on these servers, with the error.



CAUSE
SQL Server 2000 Service Pack 1 setup requires that all the databases on the server be accessible and writable.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft 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
The following table outlines some possible resolutions for databases that are in the listed states:

After the databases are in writable state, re-run the SQL Server 2000 Service Pack 1 setup.

If the server is participating in log shipping as a standby or secondary server:
 * 1) Remove log shipping.
 * 2) Recover the databases by using the information provided in the SQL Server Books Online topic &quot;Recovering a Database Without Restoring&quot;.
 * 3) Install SQL Server 2000 Service Pack 1.
 * 4) Re-establish log shipping after the service pack setup completes successfully.



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