Could you specify the steps in more detail? Are you closing the AUT before stopping the ITE, or are you just closing the ITE (this could lead to interesting effects, especially if you are using the embedded agent for example). I also can't tell whether you are explicitly starting the AUT when restarting the ITE or not. When you have the problem, does disconnecting and reconnecting to the AUT Agent help? Are perhaps 2 AUTs running at the same time?
I use embedded agent and Java written AUT. I am sure that just one AUT starts at that time. These are the steps:
1 - I install GuiDancer.
2 - Open it.
3 - Open a new work space.
4 - Cofigure it's PostGreSQL option. (My test cases are stored in a PostGreSQL database)
5 - Start AUT.
6 - Make new test cases.
7 - Close the AUT.
8 - Stop the agent.
9 - Close GuiDancer.
If I restart Guidancer with the previous work space, the agent is connected but I get the 5009: AUT start failed exception. However if I close the AUT, disconnect the agent do not close Guidancer and then reconnect the agent again AUT starts successfully. To solve this problem I open a new work space or uninstall everyting about Guidancer and do the steps above.
some suggestion for you ,I have meet the problem before, at the end I confirmed The AUT configuration and found that there is some problem at the configuration,such as the excutable File name configurated error or the file is not exit in the configurate path.I hope that my answer can help you a little.