This error is usually caused by delays in the communication between controller and agent. The following list suggests ways to achieve communication and resource efficiencies and resolve this error: Change the Monitor refresh rate from default 5 to 60 Sec Add an additional agent to the test to spread the load and reduce the work of the agent machine. The error may effect only one specific controller. Please try another controller if possible, or check the NT Event Logs to see if there are any issues with that machine. Check if any global, or very large, variables are being used. This will affect the resource usage on the machines. For another possible resolution to this issue please see "Why do I get the error LoadtestController: 3432 - Command timed out? "
↧