BUG: Coclasses That Are Marked as Noncreatable Appear in COM+ Explorer (244544)
The information in this article applies to:
This article was previously published under Q244544 SYMPTOMS
When a component is added to a COM+ application, if the coclass associated with the component is marked noncreatable in the type library, then the component appears in the COM+ Explorer.
This problem commonly occurs with Visual Basic ActiveX dynamic-link libraries (DLLs) that contain classes with their instancing property set to PublicNotCreatable. Setting the instancing property of a Visual Basic class to PublicNotCreatable marks the coclass as noncreatable in the type library. Some Visual Basic programmers prefer to create interface definitions in separate Visual Basic classes. Generally, these interface definition classes are marked PublicNotCreatable.
RESOLUTION
To work around this problem, delete such noncreatable components from the COM+ application.
For additional information about a fix for this bug, click the article number below
to view the article in the Microsoft Knowledge Base:
313582 INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 18.1
314525 Cannot Install Application Proxy with a Visual Basic Class That Is Marked PublicNonCreatable
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. MORE INFORMATION
Class that are marked as noncreatable do not support creation at the top level (for example, through ITypeInfo::CreateInstance or CoCreateInstance). An object of such a class is usually obtained through a method call on another object.
This behavior differs from Microsoft Transaction Server (MTS). Coclasses marked as noncreatable do no appear in the MTS Explorer.
| Modification Type: | Major | Last Reviewed: | 10/15/2002 |
|---|
| Keywords: | kbBug kbDSupport kbSysAdmin KB244544 |
|---|
|