FIX: 70rebind.exe for Windows 2000 and MDAC upgrades on clustered SQL Server 7.0 servers (239473)
The information in this article applies to:
- Microsoft SQL Server, Enterprise Edition 7.0
- Microsoft Cluster Server 1.0
- Microsoft Cluster Server 1.1
- Microsoft Windows NT Server, Enterprise Edition 4.0
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP4
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP5
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP6
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP6a
This article was previously published under Q239473 SYMPTOMSWhen 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. CAUSE The virtual file bindings are no longer available after
currently rebound DLL files are replaced by the new MDAC installation.
RESOLUTION
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:
301511 How to obtain the latest SQL Server 7.0 service pack
WORKAROUNDDownload 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:
219264 Order of installation for SQL Server 7.0 clustering setup
STATUSMicrosoft 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.REFERENCESFor 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: 842192 How to install SQL Server 7.0 Enterprise Edition on Microsoft Cluster Server
For possible changes or updates to the order of installation, see
the following article in the Microsoft Knowledge Base:
219264 Order of installation for SQL Server 7.0 clustering setup
For frequently asked questions (FAQs) about MSCS, visit the following Microsoft Web sites:
Modification Type: | Major | Last Reviewed: | 5/15/2006 |
---|
Keywords: | kbdownload kbbug kbfix kbsetup KB239473 |
---|
|