FIX: Subsequent attempts to activate a COM object by using the ProgID fail after an intermittent error occurs in Windows Server 2003 (920865)
The information in this article applies to:
- Microsoft COM+ 1.5, when used with:
- the operating system: Microsoft Windows Server 2003
SYMPTOMSConsider the following scenario: - In Microsoft Windows Server 2003, you activate a Microsoft Component Object Model (COM) object by using the ProgID.
- A process writes to the registry. Therefore, the object cache is invalidated.
- You call the CLSIDFromProgID function to obtain the ClassID for the COM object. Because the COM object is not in the invalidated object cache, the registry is searched.
- An intermittent error occurs when you obtain the ClassID from the registry. For example, a registry API call fails.
In this scenario, the CLSIDFromProgID function returns CO_E_CLASSSTRING. Subsequent attempts to activate the COM object by using the ProgID fail. CAUSEThis issue occurs because the COM object is stored in the object cache with an unregistered ProgID.
This problem may appear to be intermittent. A process may write to the registry again and invalidate the object cache. For example, a user may log on to the computer. If no problems occur when obtaining the ClassID from the registry, COM activation for the object succeeds.RESOLUTIONHow to obtain the hotfixThis issue is fixed in the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Package 9. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 921981 Availability of the Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 9 STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 9/29/2006 |
|---|
| Keywords: | kbfix kbQFE kbWinServ2003preSP2fix kbpubtypekc kbbug KB920865 kbAudDeveloper |
|---|
|