Breadcrumbs

List of Errors in ACC

  1. Error:
Unable to retrieve Agent Repository from the server. Please check your Internet Connection

This error occurs on Agent Repository page when there is an issue with internet connectivity.


  1.  Error starting agent.
One or more instances of the agent org-10 is already running with the same session IDs

This error occurs when an agent is already running or in an active stage with the same session ID. For example, if an agent run with session ID “X” is already active, and we try to initiate another run with the same session ID “X” at the same time, whether manually or through a schedule, this error will occur.


  1. Error getting agent details from a server in the cluster.
No available servers in cluster ACC-Test

This error occurs when we deploy an agent on a cluster that does not have any server added to it.


  1. Error bringing the server online.
Error deploying to server. No connection could be made because the target machine actively refused it. [::ffff:11.22.33.44]:8005 (11.22.33.44:8005) 

Error
System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it.


Error
Error connecting to server 11.22.33.44:8005. Error starting server performance collection on server ACCTest-11.22.33.44. No connection could be made because the target machine actively refused it.

These above errors occur when there is a connection issue between the server and ACC.
When this type of error appears, we should go to the server and check whether the SE service is running. If it is running and the error still occurs, then the server should be reconnected to ACC.





  1. Error:
Unable to retrieve backup data from the server. Error getting agent backup data from server X1. Response status code does not indicate success: 500 (Internal Server Error).

Run a job on X cluster. When the run completes, remove and deploy the agent to Y cluster, and try to Get data from run history context menu. This error will come.


  1. Error saving job schedule.
A schedule already exists for this time in the selected cluster and environment.

This error occurs when we add another schedule for the same time.