FIX: COM May Not Be Uninitialized for Worker Thread When You Use sp_OA

Attempts to call a COM object through the sp_OA stored procedures may fail with error messages that indicate:

• COM is not initialized or that COM has already been initialized with a different mode (HRESULT 0x80010106)
  
  -or-
  
  
• The worker thread may stop responding (hang) in OLE32!DllMain when called for DLL_THREAD_DETACH processing as the worker thread exits.

The latter problem may also cause SQL Server to stop responding.

To 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: NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix should have the following file attributes or later: NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

NOTE: If you are using Microsoft Data Engine (MSDE) , there is no Binn\Exe folder; therefore, you can skip the steps about copying the Sqlservr.pdb file.

Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

When you use sp_OA related stored procedures to call COM objects, SQL Server must initialize and uninitialize COM on this worker thread by calling CoInitializeEx and CoUninitialize. The initialization occurs when the first sp_OA call is made in a batch, and the uninitialization should occur at the end of the batch. In some cases, the uninitialization does not occur, and the worker thread remains initialized for COM calls.