FIX: Calls Between Configured Components Built with Visual Basic Causes Loss of Extended Error Information (255735)

The information in this article applies to:

Microsoft COM+ 1.0
Microsoft Visual Basic Professional Edition for Windows 5.0
Microsoft Visual Basic Professional Edition for Windows 6.0
Microsoft Visual Basic Enterprise Edition for Windows 5.0
Microsoft Visual Basic Enterprise Edition for Windows 6.0

This article was previously published under Q255735

SYMPTOMS

Method calls between configured components built with Microsoft Visual Basic can cause the loss of extended error information. This will result in the Err.Description property of the Visual Basic Err object having a value of "Method <method name> of object <object name> failed" when returned from a failed method call.

CAUSE

This happens when the COM+ runtime environment deactivates and releases the called component after the component calls SetAbort following an error. To get extended error information, Visual Basic calls back into the deactivated component, which causes the COM+ runtime environment to reactivate it. During reactivation, Visual Basic clears the extended error information stored by the component.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Windows 2000 Service Pack 1.

MORE INFORMATION

COM objects are said to support extended error information if they return error information through the IErrorInfo interface. The Visual Basic Err object uses the IErrorInfo interface to return extended error information.

Modification Type:	Minor	Last Reviewed:	9/26/2005
Keywords:	kbHotfixServer kbQFE kbbug kbfix kbQFE kbWin2000sp1Fix KB255735