BUG: Rebuildm.exe Utility Stops Responding When Source Directory is on a CD

View products that this article applies to.

This article was previously published under Q273572

BUG #: 236130 (SHILOH)

Expand all | Collapse all

SYMPTOMS

The Rebuild master utility (rebuildm.exe) provided with Microsoft SQL Server 2000 stops responding in the Server Configuration step if the source directory that contains data files is on a CD-ROM.

For example: <MyCDDriveLetter>:\x86\data

NOTE: You must terminate the action manually.

The following error message may occur:

Rebuild Master failed with error -1:
The error occurred during server configuration. Refer to install\cnfgsvr.out and the log\errorlog files in C:\Program Files\Microsoft SQL Server\MSSQL for diagnostic information.

Back to the top

CAUSE

Rebuildm.exe needs the original master, pubs, msdb, and northwind files (both data and log). Rebuildm.exe copies these files into the installation directory of SQL Server 2000. When the copy completes, rebuildm.exe leaves all those files with the Read-only attribute set to on, which then prevents SQL Server from starting.

Back to the top

WORKAROUND

Copy the entire \x86\data folder from the CD-ROM share to the network, and then use the network as the source directory for data files. Remove the Read-only attribute on all directories and files in the share. To do this, perform a search of the share by using *.*. Right-click to select all the returned files, click Properties, and then clear the Read-only check box.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

Back to the top

MORE INFORMATION

In the CNFGSVR.OUT file you can see the following:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ver={sql server};server=<MyServerName>;UID=<username>;PWD=<strong password>;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
driver={sql server};server=<MyServerName>;UID=<username>;PWD=<strong password>;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
driver={sql server};server=<MyServerName>;UID=<username>;PWD=<password>;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).
SQL Server configuration failed.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

In the SQL Server errorlog, you can see the following:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2000-08-30 14:04:51.22 spid3     Starting up database 'master'.
2000-08-30 14:04:51.22 spid3     udopen: Operating system error 5(error not
found) during the creation/opening of physical device 
D:\SQL2000\MSSQL\data\master.mdf.
2000-08-30 14:04:51.24 spid3     FCB::Open failed: Could not open device
D:\SQL2000\MSSQL\data\master.mdf for virtual device number (VDN) 1.
2000-08-30 14:04:51.26 spid3     Error: 5105, Severity: 16, State: 4.
2000-08-30 14:04:51.28 spid3     udopen: Operating system error 5(error not
found) during the creation/opening of physical device 
D:\SQL2000\MSSQL\data\mastlog.ldf.
2000-08-30 14:04:51.29 spid3     FCB::Open failed: Could not open device
D:\SQL2000\MSSQL\data\mastlog.ldf for virtual device number (VDN) 2.
2000-08-30 14:04:51.30 spid3     Error: 5105, Severity: 16, State: 4.
2000-08-30 14:04:51.32 spid3     Error: 5180, Severity: 22, State: 1.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Back to the top