FIX: 70rebind.exe for Windows 2000 and MDAC upgrades on clustered SQL Server 7.0 servers

When you perform operating system upgrades, such as Microsoft Windows NT 4.0 Enterprise Edition to Microsoft Windows 2000 Advanced Server, or you install operating system or Microsoft Data Access Components (MDAC) service packs or hotfixes that result in an upgrade to a new version of MDAC on a clustered server that is running SQL Server 7.0 , SQL Server requires you to rebind to the virtual SQL Server DLL files.

Warning Do not install MDAC 2.6, or later, on a clustered Microsoft server that is running SQL Server 6.5 or SQL Server7.0 . SQL Server 6.5 and SQL Server 7.0 clusters do not function correctly with MDAC 2.6, or later. However, it is ok to install MDAC 2.6, or later, on a client computer that will connect to a clustered SQL Server 7.0 computer.

As noted in the "Status" section of this article, this behavior was first corrected with Microsoft SQL Server 7.0 Service Pack 4; however, the installation of hotfixes can result in the bindings being broken. To resolve the hotfix based issue, use the workaround provided.

Here is a list of files that are subject to rebinding:

• Dbnmpntw.dll
• Sqlwoa.dll
• Sqloledb.dll
• Sqlstr.dll
• Sqlsrv32.dll
• Cliconfg.exe
• Cliconfg.dll
• Ntwdblib.dll
• Dbmsrpcn.dll

Any security patches or hotfixes that replace these files will also require rebinding.

Note If the Ntwdblib.dll or the Dbmsrpcn.dll files are replaced, you must manually rebind them. These files only exist on SQL Server 7.0 Enterprise Edition Refresh installations and they will not be included in the rebinding operation provided by the 70rebind.exe utility.

The 70rebindi.exe (for Intel) and 70rebinda.exe (for Alpha) files are self-extracting executable files that re-create the file bindings.

The virtual file bindings are no longer available after currently rebound DLL files are replaced by the new MDAC installation.

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Download and run the 70rebindi.exe or the 70rebinda.exe file. The program creates and extracts the contents of the 70rebindi.exe or the 70rebinda.exe file to the folder that you specify. After you stop the appropriate services, as referenced in the following Microsoft Knowledge Base article, you can re-establish the correct file bindings:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

Specific instructions that deal with the implementation of a rolling operating system upgrade to Microsoft Windows 2000 Advanced Server are listed later in the "More Information" section.

Note If you have Microsoft SQL Server clustering installed, and you have removed Microsoft SQL Server clustering by using the Failover Cluster Wizard before you performed the upgrade, you do not have to use this utility. All the correct bindings occur when you re-cluster the SQL Server server.

The following files are available for download from the Microsoft Download Center:

For Intel: For Alpha: Release Date: April 7, 2000

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

How to use the 70rebind.exe utility to perform a Windows 2000 rolling upgrade or MDAC version upgrade to clustered servers that are running SQL Server

1. If the active/passive cluster model is being used, pause the node that is not actively in use. If the active/active cluster model is being used, choose one of the nodes, and then pause the cluster service on that node.
2. Move all cluster resources from the paused node that needs to be upgraded to the active node.
3. Perform the operating system upgrade to the paused node.
4. After the upgrade is complete, right-click My Computer, and then select Manage.
   1. Expand the Services and Applications section.
   2. Select Services.
   3. Stop the Network Connections service. This also stops the cluster service.
5. At a command prompt:
   1. Locate the folder that contains the Rebind utility. By default, the folder is C:\Rebind.
   2. Modify the command window properties so that the screen buffer height = 500.
   3. Run the Rebind utility.
   4. Scroll up and verify that all the files were re-bound.
6. Restart the Cluster Service and Network Connections Service.
7. Close the command window, and then delete the c:\Rebind folder and its contents from this node.
8. From the node with the Cluster resources, open the Cluster Administrator and move all resources to the node where you have already performed the operating system upgrade.
9. After all the resources are online again, on the node with the new operating system installed, pause the cluster service on the node that still needs to be upgraded.Note The Microsoft Distributed Transaction Coordinator (MS DTC) is a resource that is installed and used by SQL 7.0 for database replication. For instructions on how to upgrade this resource to work with a Windows 2000 Server Cluster, view the section titled "Upgrading the MS DTC Resource" in the Microsoft Windows 2000 Release Notes that can be found in the root folder of the Windows 2000 media in the Readme.doc file.
   
   
10. Perform the operating system upgrade to the paused node.
11. When the upgrade completes, right-click My Computer, and then click Manage.
    1. Expand the Services and Applications section.
    2. Click Services.
    3. Stop the Network Connections service. This also stops the cluster service.
12. At a command prompt:
    1. Locate the folder that contains the rebind utility. By default, the folder is C:\Rebind.
    2. Modify the command window properties so that the screen buffer height = 500.
    3. Run the Rebind utility.
    4. Scroll up and verify that all files were re-bound.
13. Restart the Cluster Service and Network Connections Service.
14. Close the command window and delete the rebind utilities from this node.
15. Test cluster failover and SQL Server functionality.

When you perform an upgrade of your operating system, an alternate procedure is as follows:

1. Remove Microsoft SQL Server clustering, by using the Failover Cluster Wizard. Make a note of all the resource names, IP addresses, network names in use and all the cluster specific information for Microsoft SQL Server before removing Microsoft SQL Server Clustering components.
2. Perform the operating system upgrade.
3. Reinstall Microsoft SQL Server clustering by re-running the SQL Cluster Wizard.

For a step-by-step guide to installing Microsoft SQL Server 7.0 Enterprise Edition on Microsoft Cluster Server (MSCS), see the following article in the Microsoft Knowledge Base: For possible changes or updates to the order of installation, see the following article in the Microsoft Knowledge Base: For frequently asked questions (FAQs) about MSCS, visit the following Microsoft Web site: