Common Agent Issues

How to resolve an issue when an Agent is not reporting any testing results.

Summary

  • Category: Agent issues
  • Environment: Any
  • Severity/Impact: Critical
  • Status: Known issue, Configuration issue

Symptoms

The Agent is not reporting any testing results.

Causes and Resolutions

The following table applies to all Agents regardless of their technology.

Cause Resolution
The Agent is not connected to the Seeker server because of a connectivity issue or an unexpected error.
  • Check the Agent logs for connectivity issues between the Agent and server.

    For log locations, see Agent Logs.

  • Use the Seeker diagnostic utility to check the connectivity to the server.

    For instructions, see Use Diagnostic Utility.
The Agent is connected but is not reporting any results, because it doesn't support the runtime framework on which the application is running. Check if the runtime framework that you are using is supported by the respective Seeker Agent:
The Agent is connected but is not reporting any results, because it is not installed in the actual environment that is being tested. For example, when the application's entry point is a load balancer that dispatches calls to several nodes, on which the Agent is not installed. Make sure to install a Seeker Agent in each environment that you are going to test.
Note: If none of the listed resolutions works for your particular case, see the technology-specific sections of this guide.