Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

What are the errors which can occur when the loadtest controller attempts to connect to agents?

What are the errors which can occur when the loadtest controller attempts to connect to agents?

What are the errors which can occur when the loadtest controller attempts to connect to agents?



What are the errors which can occur when the loadtest controller attempts to connect to agents?



1) Loadtest Controller - 3211: Could not connect agent control service:

a) The Launcher service is not running
-> Solution: Start the Launcher service

b) A port mismatch happens (i.e. the port the agent is listening on and the port the controller wants to connect the ACS are different)
-> Solution: Adjust the agent connection settings

c) The agent is connected through a proxy and the proxy is down
-> Solution: Check the agent connection settings / restart the proxy

d) Communication timeout between MMC and agent machine
-> Solution: If the agents are distributed across a Wide Area Network (WAN) the remote agent connection properties should be optimised for a WAN (Settings | System | Control). If the network connection is not stable or has a low bandwidth available you can increase the timeout values by choosing the "Custom" option (not recommended).

 

2) Loadtest Controller - 3212: Could not authenticate at agent control service

The agent requires a password and encryption is enabled. The agent"s server certificate could not be found, or a required dll is missing (e.g. ssleay32.dll). However, the ACS doesn"t report an error at startup, if this is the case.
->Solution: Best to reinstall the remote agent, because the missing certificate or dlls indicate that the agent was probably not installed correctly.

 

3) Loadtest Controller - 3213: The agent control service could not create the agent

Same as 2, except the agent doesn"t require a password.

 

4) Loadtest Controller - 3233: The agent"s version doesn"t match the version of its controller

-> Solution: Install the correct remote agent version

 

5) Loadtest Controller - 3303: The local results directory could not be created

This is an access rights problem i.e. the user-account of agent process (mostly = system account) doesn"t have the necessary access rights to create a directory (most likely the parent directory of the desired directory is read-only for all accounts)
-> Solution: Grant the necessary access rights

 

6) Loadtest Controller - 3304: The local results directory could not be cleared

A file within the local results directory is still opened by another process (most likely the perfLtcAgent.exe and perfRun.exe). This usually indicates that either the agent or the runtime processes did not shutdown at the end of a previous loadtest, which should not happen.

-> Solution: Check for pending perfLtcAgent.exe or perfRun.exe files and terminate them manually.
If this is not the case, check for other programs, holding open a file within the local results directory.
If this is not the case, reboot the remote agent"s machine.

 

7) Loadtest Controller - 3305: The local data directory could not be created

Reason and solution is the same as 5)

 

8) Loadtest Controller - 3306: The local data directory could not be cleared

Reason and solution is the same as 6)

 

9) SilkPerformer - 32: Access denied, authentication required

The agent expects a password but the controller didn"t send any password, i.e. didn"t authenticate itself
-> Solution: Adjust the agent connection settings

 

10) SilkPerformer - 33: Authentication failed (wrong password)

The agent expects a password but the password sent by the controller is incorrect.
-> Solution: Adjust the agent connection settings

 

11) SilkPerformer - 25: Limit of concurrent instances exceeded

Two agent"s cannot run simultaneously. Most likely, the agent is involved in a loadtest started by another controller.

-> Solution: Try again (wait for the other controller to finish its loadtest)
If this is not the case, the agent did not terminate correctly at the end of a previous loadtest -> terminate the agent process manually.

 

12) System - 2: The system cannot find the file specified

The agent executable (perfLtcAgent.exe) could not be found, or there is a different entry for the agent executable in the performerLocal.ini file.
->Solution: Check the performerLocal.ini file, if it is correct, check if the perfLtcAgent.exe is present, if not, reinstall the agent.

 

12) Loadtest Controller - 3422: Command timed out

a) Usually the controller has 30 seconds to

- connect the remote agent control service
- pass authentication information to the remote agent control service (if required)
- ask the agent control service to create the agent
- connect the agent
- exchange version information with the remote agent

It might happen that these tasks take more time than the default timeout of 30 seconds, especially if the agent is connected through a proxy, or the connection is slow for any reason.

-> Solution: Specify a greater timeout in the system settings (System Settings | Control | Remote Agent Connection)

13) Loadtest Controller - 3223: Agent connection lost

This happens, whenever the connection is broken between controller and agent for some reason or the underlying communication units of the loadtest controller (perfOrb,....) report any connection troubles.
Furthermore, connecting the agent through a proxy might be the reason for the error since the proxy itself may be buggy (e.g. Netscape proxy,...)

->Solution: There should be log files named orbClient_.log, orbServer_.log in the controller"s or agent"s home-directory respectively where logging information according to the error can be found. Check this info and forward to Support.

This error can also occur for the following reason:
Processing errors on an agent uses CPU and IO resources, which negatively influences the agents capability to respond to the controller"s request to update the monitor data.
The controller tries to request the monitor data only a certain number of times. When these requests time out the controller thinks that the connection does not work any more and closes the connection to the agent resultng in the "Loadtest Controller - 3223: Agent connection lost" error.
A possible resolution for this is to either reduce the load on the agent by reducing the number of vusers or try to re-start a transaction in case of an IIOP error.

 

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments

Hi,

Can you provide instruction to debug loadtest Controller 3235 - Could not transfer datafiles to agent

Thanks.

Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:04
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.