PRB: SQL Server May Appear to Stop Responding Upon StartupLast reviewed: October 21, 1997Article ID: Q175398 |
The information in this article applies to:
SYMPTOMSSQL Server starts successfully, but any attempt to connect to it is unsuccessful. It appears as if the server has stopped responding.
CAUSEThe automatically executed sp_sqlregister stored procedure calls the xp_sqlregister extended stored procedure. The DLL that contains this extended stored procedure has additional functions that depend on Open Database Connectivity (ODBC). If the versions of Odbcint.dll and Odbc32.dll on the computer are different, the ODBC Driver Manager produces the following message:
The ODBC resource DLL(C:\WINNT\System32\odbcint.dll) is a different version than the ODBC driver manager (C:\WINNT\System32\ODBC32.dll). You need to reinstall the ODBC components to ensure proper operation. PRESS OK to proceed, CANCEL to abort.The problem occurs when SQL Server is running as a service without the "Allow Service to Interact with Desktop" check box enabled. If this is the case, the warning dialog box described above goes to the virtual desktop, so you never see it. Because you can't see it, you can never press OK to continue, so it appears that the server has stopped responding.
WORKAROUNDTo permanently resolve this problem, update your ODBC components so that they all have the same file versions. To temporarily work around this problem, do any one of the following:
|
Additional query words: hang hung xproc sproc stproc autoexec startup
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |