We have a web application (ASP) that needs to read data from Test Director. We are, however, unable to register the OTAclient on Windows Components Services for the ASP and OTA to work.

Mercury advised us as follows:
"The only COM component that you need to register is TDConnection. The references to all the other objects in the OTA API is acquired via the TDConnection object. TDConnection is like a Factory Class. Can we register TDConnection alone and try the application?"

We tried to ignore the registration errors and tried anyway, but we think that the failed registration of the DLL is still causing a COM Surrogate error as attached (ComSurrogate.ZIP).


The event log obtained using the Event Viewer for the said error messages have the following details:

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID:
Server Application ID: {D797D97E-0D40-4723-BD99-0F38F0CDC685}
Server Application Instance ID:
Server Application Name: MSDW
The serious nature of this error has caused the process to terminate.
Exception: E06D7363
Address: 0x77E73887
Call Stack:
kernel32!RaiseException + 0x50
OTAClient80! + 0x1C6B8C
OTAClient80! + 0x8365D
OTAClient80! + 0x15E699
OLEAUT32!DispCallFunc + 0x165
OLEAUT32!VarBstrFromDec + 0x771A
OTAClient80! + 0x15773C
OLEAUT32!LPSAFEARRAY_UserUnmarshal + 0x771 ! + 0x6F0069