If a SilkTest Agent only installation does not correctly load extensions, how can this be resolved?
While testing with remote and local Agents, SilkTest is unable to correctly load the extensions in an Agent only machine. For example, while playing back an IE 6 DOM testsuite, SilkTest returned the typical 'Error: Window not found'. Whereas the local Agent (with full SilkTest installation) played back smoothly with the same configuration as the remote Agent.
By right-clicking on the Agent whilst the test is trying to execute, the expected domex.dll is not loaded in the remote Agent. Instead, a custom dll extension is seen to be loaded. In contrast, the local Agent had domex.dll loaded and played back without incident.
A few instances of this have been reported, although it has not been possible to replicate in-house to date. As a workaround to resolve this issue on the remote machine, please uninstall the SilkTest Agent installation, reboot and install the full SilkTest package. This was found to resolve this extensions issue on Agent only installs. Since you will still only be using the Agent part of this installation and not the main SilkTest GUI, you will only require and use one SilkTest Agent license.