That's annoying, sorry!
My only other suggestion, is to log a support call - TestComplete: New Support Request
ok. perhaps this is the root cause. on my remote machine i have testexecute set up to only start up when a test starts running on the remote (either via my CI tool or via Network Suite from my workstation). TestExecute is not running 24x7. are you saying that the testexecute on my remote machine (not testcomplete) has to be running in order for me to add the performance counters in the testcomplete in which i'm doing the development on my local workstation? if so, then does testexecute have to remain running or can i go back to the "run only when needed" state after the counters have been added?
i'm going to go ahead and start up testexecute on the remote machine and see how that affects my being able to add counters in the testcomplete on my workstation. will let you know how that turns out
even with testexecute up and running on the remote, i still get the same error on my testcomplete when i attempt to add a standard counter on that remote IP address
