FIX: SQL Server 2000 Service Pack 1 Setup May Fail when Applied to a Server with Non-writable Databases
This article was previously published under Q300919
BUG #: 353868 (SHILOH_BUGS)
On This PageSYMPTOMS
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:
CAUSE
SQL Server 2000 Service Pack 1 setup requires that all the databases on the server be accessible and writable.
RESOLUTIONTo 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 (http://support.microsoft.com/kb/290211/EN-US/) 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:
STATUSMicrosoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2. REFERENCESRefer to Section 3.0 of the Sp1readme.htm file included with the Service Pack 1 installation files for more information about this problem.For additional information about removing log shipping when a database name contains a quote character, click the article number below to view the article in the Microsoft Knowledge Base: 295936 (http://support.microsoft.com/kb/295936/EN-US/) FIX: Error Removing Log Shipping on Secondary Database When Database Name Has a Quote
For more information about databases in a SUSPECT state, refer to the following Microsoft Knowledge Base articles:
180500 (http://support.microsoft.com/kb/180500/EN-US/) PRB: Missing Device Causes Database to Be Marked Suspect
257852 (http://support.microsoft.com/kb/257852/EN-US/) INF: How to Recover from a "File in Use" Situation on SQL Server Startup
165918 (http://support.microsoft.com/kb/165918/EN-US/) INF: Bypass (Emergency) Mode and DUMP TRANSACTION WITH NO_LOG
288809 (http://support.microsoft.com/kb/288809/EN-US/) PRB: How to Recover SQL Server After a Tempdb Database is Marked Suspect
| Article Translations
|

Back to the top
