Some questions ...
<ul type="square">[*]What version of TestPartner are you using?[*]What is the application under test?[*]Did TestPartner create a crash dump? [*]If you did get a crash dump, did you contact Compuware support and supply the crash dump to them?[/list]
From previous posts, it was said that an ailing application may cause TestPartner to crash. Note that TestPartner installs hooks with the application.
On another note, I have observed that TestPartner crashes quite a lot in Vista and Windows Server 20008. May I ask other folks here to check "Problems Reports and Solutions" in Windows Vista and Windows 2008? That guy reports that "TestPartner" is crashing almost everytime. Oh I am using tp.exe to run the tests.
We had a crashing problem as well which turned out to be an issue with our TP server. It was dropping the SQL connection on heavy usage which will cause TP to crash. Once we updated our network card driver, the SQL connection stayed up and TP stopped crashing.
Even I was facing crash problem previously when I was using TP 5.3. And Now I have upgraded that to 6.0 version. My problem is resolved. Now I am able to run same application. This might be issue with you. You can check your version.
How did you detect that you were dropping the sql connection?
I created an automation script that essentially functions as a production monitoring script. It executes various scripts against a production app to ensure that the app is up and running and we haven't lost connectivity to other components of the app. The script runs in an infinite loop and crashes quite often [script is invoked via a batch script/command prompt].
I attributed it to the fact that we are the TestPartner db is an access db and it is quite limited and we are probably using up too many resources on the server. Of course, this is based on any proof - just my best guess.