Benchmark Factory Job Error: "Not All Configured Agents Have Connected in a Timely Manner" (4379702)

Benchmark Factory requires that all configured agents (local and remote) be connected and communicating with the console before a test can proceed. This error typically arises when:

• A remote agent is not properly defined or configured.
• A required port is blocked by a firewall.
• The console cannot locate or communicate with Agent.exe or BMFAgent.exe.

By default, the local agent is pre-configured during installation. However, remote agents must be manually defined and linked to the console. Each agent is responsible for returning load testing data to the console.

1. Verify Agent Configuration

• Local Agent: Ensure the local agent is configured with the IP address or hostname of the local machine.
• Remote Agent:
  • Define the remote agent connection within the Benchmark Factory Console.
  • Ensure the agent machine has the correct console IP/hostname configured in Agent.exe (Options > Settings > Machine Name/IP).
  • Confirm that the agent knows the correct Console Port and Max Virtual Users settings.

2. Start the Agent Manually (if needed)

• Navigate to:
  Program Files\Quest Software\Benchmark Factory <version>\bin
• Double-click Agent.exe to manually start the agent.
• Use the Agent console GUI to view and configure connection settings.

3. Configure Windows Firewall Rules

On the Console Machine (Inbound Rule)

• Open:
  Control Panel > System and Security > Windows Firewall > Advanced Settings
• Create a new Inbound Rule for TCP port 4568.
• Apply the rule to Domain, Private, and Public networks.

On the Agent Machine (Inbound Rule)

• Repeat the steps above.
• Create an Inbound Rule for TCP port 135.

On the Agent Machine (Outbound Rule, if required)

• If outbound traffic is restricted:
  • Create an Outbound Rule for TCP port 4568.
  • Allow the connection on all network profiles (Domain, Private, Public).

Note: Outbound traffic is allowed by default in Windows Firewall. Only add an outbound rule if connections are being blocked.

4. Confirm Agent Status

• After completing the configuration, re-attempt the test run.
• If the error persists, verify network connectivity between the console and the agent machine (e.g., via ping or telnet to port 4568).