Not sure if this is solved, but here is a possible solution:
When you log into your Siebel app, you should be starting two Siebel Active X components: Desktop Integration and Test Automation.
The initial login URL may contain the commands to start the Test Automation component, which is found on the server. For example
After logging out, the login URL may be different so that the Test Automation component is no longer loaded.
Try this manually along with Task Manager and see what processes remain running after logout.
Good luck,
H
When you log into your Siebel app, you should be starting two Siebel Active X components: Desktop Integration and Test Automation.
The initial login URL may contain the commands to start the Test Automation component, which is found on the server. For example
Code:
"SWECmd=AutoOn&AutoToken=password."After logging out, the login URL may be different so that the Test Automation component is no longer loaded.
Try this manually along with Task Manager and see what processes remain running after logout.
Good luck,
H
