Hi,
If I attempt to stop a test using Shift+F2 or clicking [Stop] I often get a "stopping..." message which prevents further use of TC.
I have attempted the performance optimisations and filtering the object map to tested applications, and turning off non-essential addins. I have extended search turned on for a couple of objects but turning this off does not make any difference.
It happens with local test runs and network executions.
I have never seen it happen on tiny project suites, only my production version.
It never seems to happen with a stand-alone TestExecute agent, unless it's slaved to a a TC master in which case it stalls both TC and TE.
Any ideas would be welcome
Thanks
Jonathan