How to rebuild the master database on a SQL Server 2000 (64-bit) cluster (817232)

MORE INFORMATION

To rebuild the master database, you must have the Product ID (PID) that was used to install SQL Server 2000 (64-bit). The PID is a GUID that is stored in the registry. For a default instance of SQL Server 2000 (64-bit), the PID is in the registry under:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\Setup\ProductCode

For a named instance of SQL Server 2000 (64-bit), the PID is in the registry under:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance name>\Setup\ProductCode.

When you rebuild the master database, you can configure:

• The sa password
• Collation
• Cross-database ownership chaining
• Error reporting

If you make changes to the authentication mode, they will not be reflected after the server is reinstalled. However, you can change the authentication mode after the reinstallation is complete.

You must complete all these steps from the cluster node that owns the SQL Server resource.

To rebuild the master database of a default instance of Microsoft SQL Server 2000 (64-bit), use these steps:

1. Take the SQL Server virtual server offline.
2. In Registry Editor, under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\<PID>, make these changes:
   1. Change the SqlCluster value to 0, and note the value of SqlCLusterSec.
   2. Change the value of SqlClusterSec to 0.
   Note You must restore the value of SqlClusterSec after you rebuild the master database.
   
   <PID> is the PID of the Windows Installer package that was used to install SQL Server.
3. Run Cliconfg.exe to start the Client Network Utility:
   1. On the Alias tab, click Add. The Add Network Library Configuration dialog box opens.
   2. For Network Libraries, click to select the Other option button.
   3. In the Server alias text box, type <computer name>, where <computer name> is the name of the local computer. For a named instance, type <computer name>\<instance name>, where <computer name> is the name of the local computer, and <instance name> is the name of the instance of SQL Server. The local computer must be the cluster node that owns the SQL Server resource.
   4. In the File name text box, type DBNETLIB.
   5. In the Parameters text box, type lpc:<virtual server name>. For a named instance, type lpc:<virtual server name>\<virtual server instance name>, where <virtual server name> is the name of the SQL Server virtual server, and <virtual server instance name> is the named instance of the SQL Server 2000 (64-bit) virtual server.
   6. Click OK.
4. Run Msiexec.exe to rebuild the master database.
   
   From the command prompt, type the following:

   msiexec.exe /i <PID> REINSTALL=ALL REINSTALLMODE=amus SQLAUTOSTART=0 /L*v <path and File_name.txt>

   Note <PID> is the PID of the Windows Installer package that was used to install SQL Server, and <path and Filename.txt> is the location and the file name for the verbose log file.
   
   For example, type the following command:

   msiexec.exe /i {0F34966C-4EF4-45AE-B78E-486BEFB71698} REINSTALL=ALL RENSTALLMODE=amus SQLAUTOSTART=0 /L*v rebuildmaster.txt

   For example, type d:\rebuild_master_verbose_log.txt. The reinstallation dialog box appears. Make any changes to the sa password, collation, cross-database ownership chaining, and Watson. If you make changes to the authentication mode, they will not be reflected after the server is reinstalled. You can change the authentication mode after the reinstallation is complete.
   
   Note In some situations, the computer may display a message that states that file operations are pending, and you are prompted to restart the computer. Click No.
5. In Registry Editor, under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\<PID>, change the SqlCluster value to 1. Restore the value of SqlClusterSec to the value you noted in step 2.
6. Run Cliconfg.exe to open the Client Network utility. On the Alias tab, select the server alias that you created in step 3, and then click Remove.
7. If the computer requests a restart, restart the computer that is running SQL Server now.
8. Bring the virtual server online.