PRB: COM+ WSC Component Cannot Raise Error After SetAbort (285147)
The information in this article applies to:
- Microsoft COM+ 1.0, when used with:
- the operating system: Microsoft Windows 2000 SP1
- the operating system: Microsoft Windows 2000 SP2
This article was previously published under Q285147 SYMPTOMS
When a Windows Script Components (WSC) component is configured under COM+, COM+ controls the script component. When the script aborts a transaction and then throws an error, an access violation occurs.
This problem only occurs when JScript is the scripting language and the transaction attribute is set to Required.
CAUSE
This problem occurs because the error object that is associated or caught in the WSC exception is actually a reference to the script object itself. This design does not comply with COM+ policy, which does not allow access to a configured component once the transaction that is associated with the component has aborted.
RESOLUTION
At this time, there is no resolution for this problem. A fix will be available in a later version of Windows.
STATUS
This behavior is by design.
REFERENCESFor additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
275293 FIX: DLLHOST Process Ends When Transacted WSC Components Are Called from IIS
Modification Type: | Major | Last Reviewed: | 6/5/2003 |
---|
Keywords: | kbprb KB285147 |
---|
|