Microsoft KB Archive/175398
Article ID: 175398
Article Last Modified on 10/3/2003
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q175398
SQL Server starts successfully, but any attempt to connect to it is unsuccessful. It appears as if the server has stopped responding.
The 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 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.
To 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:
- Enable trace flag 4022 (-T4022) in the startup parameters, to bypass the startup stored procedures.
- Change the startup account to system account with the "Allow Service To Interact With Desktop" option enabled so that you can get the warning message and press OK to continue.
- Start SQL Server from a command prompt with the -c option.
- Replace the Odbcint.dll and odbc32.dll files with those from Windows NT 4.0 Service Pack 3.
Additional query words: hang hung xproc sproc stproc autoexec startup
Keywords: kbinterop kbenv kbprb KB175398