INF: Incorrect Versions of Odbcint.dll Can Affect Components

In some situations the ODBC DLL file, Odbcint.dll, is no longer synchronized with the other ODBC DLLs. This can cause an Odbcint.dll version error to occur when you start ODBC-dependent applications. When you start an ODBC application, you receive the following error message:

In most situations the client application continues to function partially or it may not function at all. The functionality losses or abnormal behavior can vary widely from application to application.

Odbcint.dll version problems can also affect SQL Server and SQL Executive. For additional information about the effects on the SQL Server service, please see the following article in the Microsoft Knowledge Base:



When the SQL Executive service is affected, it does not start scheduled tasks and does not shut down correctly when you issue a service shutdown request. When you try to execute any task, you receive the following error message:

ODBC problems can also affect SQL Server extended stored procedures. When you restart the SQL Server service, if you click Cancel when the error message about the DLL mismatch appears, a call to either xp_cmdshell or xp_logevent may cause the server to freeze. Existing connections to the server are not allowed to proceed and new connections to the server can not be made. You must restart the server. If you click OK on the error message dialog box, then subsequent calls to xp_cmdshell or xp_logevent are honored.

By default, the SQL Server service is started using the local system account and is allowed to interact with the desktop. When SQL Server is started, an error message warning of the Odbcint.dll mismatch is displayed, however the SQL Executive service is set up to start under a given account and not interact with the desktop. When SQL Executive starts, it does not display the error message warning of the Odbcint.dll mismatch.

SQL Executive appears to be working in the SQL Service Manager and the SQL Enterprise Manager but no tasks can be started. Starting tasks from the Enterprise Manager or executing xp_schedulersignal gives error 21003 (see the "Symptoms" section).

To permanently resolve this problem, update your ODBC components so that they all have compatible file versions. To do this, quit all ODBC-related applications and reinstall ODBC. The ODBC setup files that are included with SQL Server are available on the SQL Server CD in the \i386\ODBC directory.

For additional information, please see the following article in the Microsoft Knowledge Base: