FIX: SQL Server 2000 SP1 installation on a cluster with the Sqlservr.exe file fails with an "Entry point not found" error message (306034)
The information in this article applies to:
- Microsoft SQL Server 2000 Enterprise Edition SP1
- Microsoft SQL Server 2000 Enterprise Evaluation Edition SP1
- Microsoft SQL Server 2000 Developer Edition SP1
This article was previously published under Q306034
BUG #: 353796 (Shiloh_bugs)
SYMPTOMS
During a Microsoft SQL Server 2000 Service Pack 1 (SP1) installation in a cluster, when the Setup program tries to run scripts against the server, the Setup fails with the following error message:
Title - sqlservr.exe - Entry Point Not Found
FindNextAvailable@UmsSchedulerQueue@@QAEPAVUmsScheduler@@W4UmsSchedulerAlgorithms @@@Z could not be located in the dynamic link library UMS.DLL.
The only way to exit the message box is to click OK.
The event is logged to the System event log of the computer as:
8/10/2001 10:47:07 PM 4 0 26 Application Popup
N/A Your_Node_Name Application popup: sqlservr.exe - Entry Point Not
Found : The procedure entry point
?FindNextAvailable@UmsSchedulerQueue@@QAEPAVUmsScheduler@@W4UmsSchedulerAlg
orithms@@@Z could not be located in the dynamic link library UMS.DLL.
8/10/2001 10:47:37 PM 1 0 7009 Service Control
Manager N/A Your_Node_Name Timeout (30000 milliseconds) waiting for
the MSSQLSERVER service to connect.
8/10/2001 10:47:37 PM 1 0 7000 Service Control
Manager N/A Your_Node_Name The MSSQLSERVER service failed to start due
to the following error: %%1053
8/10/2001 10:47:37 PM 1 4 1069 ClusSvc N/A
NodeName Cluster resource 'SQL Server' failed.
CAUSE
The Sqlservr.exe file cannot be replaced as required because the file is being detected as in use.
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 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
Navigate to the SQL Server Binn folder on the node from which you are installing SQL Server 2000 SP1 and locate the Sqlservr.1 file.
If Sqlservr.1 exists, rename Sqlservr.exe to Sqlservr.old and rename Sqlservr.1 to Sqlservr.exe. Now, run the SQL Server 2000 SP1 installation again.
After the SQL Server 2000 SP1 installation completes, delete the Sqlservr.old file.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000 Service Pack 1.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
| Modification Type: | Minor | Last Reviewed: | 3/14/2006 |
|---|
| Keywords: | kbQFE kbbug kbfix KB306034 kbAudITPRO kbAudDeveloper |
|---|
|