LoadtestController: 3221 - Could not connect agent
When displayed with a ‘LoadtestController:: 3221 could not connect to agent’ error at the beginning of a load test, it means that there have been issues with agent communication / connectivity.
There are various reasons why the error is rendered, some of which are detailed below:
1. Firstly the error can occur because Silk Performer, when connecting to an agent machine, requires two ports to be open for the agent communication to take place, these ports are 19200 and 19202.
If the ports are not open, then agent connectivity will fail and result in the 3221 error.
For further information on the communication process refer to the ‘Remote Agent’ section of the Silk Performer User Guide – Page 41.
2. Another reason for the error, can be if there is an additional entry in the AppInit_DLLs key on the agent machine. This key can be found within the following locations:
This value for this registry key should be blank. If there are additional values in this key they should be removed.
3. By default during a loadtest, agent processes are launched under a systems account. If the System account for this remote system does not have the relevant permissions to start these agent processes, for example perfRun.exe, perfLtcAgent.exe , then the ‘LoadtestController: 3221 - Could not connect agent’ error is the result.
If a certain user is required to start these processes, then specifying a user account within SILK PERFORMER | SETTINGS | SYSTEM | AGENTS | ADVANCED, means that the agent processes are launched under that specific user rather than the system account.