FIX: Calls Between Configured Components Built with Visual Basic Causes Loss of Extended Error Information
This article was previously published under Q255735
This article has been archived. It is offered "as is" and will no longer be updated.
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.
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.
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 theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
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.
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.
Article ID: 255735 - Last Review: 02/28/2014 00:31:19 - Revision: 1.3
Microsoft COM+ 1.0, Microsoft Visual Basic 5.0 Professional Edition, Microsoft Visual Basic 6.0 Professional Edition, Microsoft Visual Basic 5.0 Enterprise Edition, Microsoft Visual Basic Enterprise Edition for Windows 6.0
- kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000sp1fix KB255735