Article ID: 283876
Article Last Modified on 8/23/2001
APPLIES TO
- Microsoft Transaction Services 2.0
This article was previously published under Q283876
SYMPTOMS
When you try to export a package that contains a Microsoft Visual Basic ActiveX dynamic-link library (DLL), you may receive the following error message:
CAUSE
When you add a method to an ActiveX DLL in Visual Basic for which the binary compatibility option has been set, Visual Basic creates a new interface ID (IID) and adds forwarding entries for the old interface. This error indicates that the forwarding chain is corrupt or that MTS can no longer follow the chain.
RESOLUTION
To resolve this problem, follow these steps:
- Under the Component tab of the Project Properties dialog box, click No Compatibility in the Version Compatibility list. This generates a new globally unique identifier (GUID) for the interface without the forwarding chain the next time that the DLL is compiled.
- Recompile the Visual Basic DLL.
- In the project settings, reset the Version Compatibility to binary compatibility.
- Register the component again with MTS.
STATUS
This behavior is by design.
REFERENCES
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
281630 HOWTO: Configure Visual Basic DLL Project Properties to Run in IIS, MTS, or COM+
241637 PRB: Adding a New Method to a VB Component in MTS Breaks Existing Client
Additional query words: 80110421
Keywords: kberrmsg kbprb KB283876
