When we run QTP scripts from QC that tries to navigate to and verify the presence of the Terminal Emulator embedded in a web-application, the TE fails to start. Once the link is hit on the web-app, which navigates to the page that has the TE embedded, we get pop-ups with "Program Launch Failed/Error Codes" etc...

Details of the TE:

Vendor: Seagull Emulator : BlueZone3.2

When the same test is run manually, the problem is not encountered. I am of the view that:

1.QC, QTP, web-app drain the resources hugely to let the TE to start

Or 2. QC or QTPs software hinders the launch of TE. Could the automation agent or OTAClient.dll cause the problem?

Has anybody come across this problem?