When might I see "COM Replay: 105 - Couldn"t resolve reference type" or "COM Replay 203 - No Definition for " <interface parameter>" errors on replay ?
Such errors can occur when the Silk Performer COM replay engine is either unable to resolve a reference type while parsing a type library, or cannot find the type library that defines the required interface.
A reference type in a type library is used when a parameter of a COM function is not directly declared in the type library where the function is declared, instead the parameters type declaration is just a reference to the actual type definition in another type library.
In order to get all needed information, the COM replay engine needs to follow this reference and check the full type definition in the corresponding type library.
Always ensure that all required type libraries are added to the Interface dialog when setting up you COM client"s application profile in Silk Performer.
If you are unsure what type libraries are needed then contact the developers of the application. SilkPerformer may also be able to provide some details on missing type libraries, please see How can I identify missing type libraries when trying to record my COM application ?
If you are having difficulties with recording or replaying COM / ADO then please contact
NOTE: Since the introduction of GUI-level testing in Silk Performer 2006 Release 2, it may be possible to loadtest applications that are not supported by Silk Performer on the protocol- or API-levels by recording on the GUI level. The link below is an introduction to GUI-Level Testing within Silk Performer: