List of Errors in ACC | Sequentum Enterprise Help Center

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.

Steps to replicate:

Log in to ACC and open the Agent Repository page.
Disconnect the internet connection (turn off Wi-Fi or unplug the network cable).
Refresh the page or navigate within ACC. This error will come.

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. For a manual run, this check is skipped when the multiple sessions option is enabled.

Steps to replicate:

Start an agent run with session ID “X”.
While the run is still active, start another run of the same agent with the same session ID “X” (manually or through a schedule). This error will come.

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

This error occurs when we open Run Agent for an agent that is deployed on a cluster that does not have any server added to it (ACC cannot fetch the input parameters and sessions from a server).

Steps to replicate:

Create a cluster (e.g., ACC-Test) and do not add any server to it.
Deploy an agent to this cluster.
Click Run Agent for this agent. This error will come.

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.

Steps to replicate:

Add a server to a cluster in ACC.
Go to the server and stop the SE service.
In ACC, try to bring the server online or deploy an agent to it. These errors will come.

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).

This error occurs when we try to get the data of a run from a server that no longer has the agent, for example after the agent is moved to another cluster.

Steps to replicate:

Run a job on cluster X and wait for the run to complete.
Remove the agent and deploy it to cluster Y.
Go to Run History, right-click the completed run and select Get data. This error will come.

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.

Steps to replicate:

Add a schedule for a job at a specific time in a cluster and environment.
Add another schedule for the same time in the same cluster and environment and save it. This error will come.

Agent could not be deleted.
Unable to delete agent because it has associated server deployments. Please delete all server deployments first.

This error occurs when we try to delete an agent that is still deployed to one or more servers.

Steps to replicate:

Deploy an agent to a server.
Go to Agent Repository and delete the agent without removing the server deployment. This error will come.

Agent could not be deleted.
Unable to delete agent because it has an associated cluster deployment. Please delete the cluster deployment first.

This error occurs when we try to delete an agent that is still deployed to a cluster.

Steps to replicate:

Deploy an agent to a cluster.
Go to Agent Repository and delete the agent without removing it from the cluster. This error will come.

Agent version could not be deleted.
The Agent Repository must have at least one version of an agent. Delete the agent if you want to remove all versions.

This error occurs when we try to delete the only remaining version of an agent.

Steps to replicate:

Select an agent that has only one version in Agent Repository.
Open the agent versions and delete that version. This error will come.

Error:
Version conflict. You're checking in an agent that has been modified by someone else since you got the latest version. You must get the latest version and then make your changes, or ignore conflicts when you check in.

This error is shown in Sequentum Enterprise during check-in when an agent is checked in from an older version after someone else has already checked in a newer version.

Steps to replicate:

User A and User B both get the latest version of the same agent from ACC in SE.
User A makes a change and checks in the agent.
User B makes a change and checks in the agent without selecting ignore conflicts. This error will come.

Error:
An agent with the same name already exists in this directory

This error is shown in Sequentum Enterprise during check-in when we check in a new agent with a name that already exists in the selected directory.

Steps to replicate:

Create a new agent in SE with the same name as an existing agent in an ACC directory.
Check in the new agent to the same directory. This error will come.

Error:
Schema error. The agent does not conform to the directory schema. You must correct the agent or ignore schema when you check in.

This error is shown in Sequentum Enterprise during check-in when the directory has an export schema and the agent's export tables/fields do not match it.

Steps to replicate:

Set an export schema on a directory in ACC.
Change an export field (name, data type, etc.) of an agent in SE so it does not match the schema.
Check in the agent to that directory without selecting ignore schema. This error will come.

Error removing agent from cluster.
The agent cannot be removed from the cluster because it's current running. Please stop all running instances of the agent first.

This error occurs when we try to remove an agent from a cluster while the agent is running.

Steps to replicate:

Deploy an agent to a cluster and start a run.
While the run is in progress, remove the agent from the cluster. This error will come.

Run history could not be deleted
Unable to delete run history that is part of a job. Delete related job history instead.

This error occurs when we try to delete a run from Run History that belongs to a job.

Steps to replicate:

Run an agent job and let the run complete.
Go to Run History and delete that run. This error will come.

Run history could not be deleted
Unable to delete an agent run that is in progress. Manually set the agent run to failed or succeeded first.

This error occurs when we try to delete a run that is still running.

Steps to replicate:

Start an agent run with a custom Run ID.
While the run is in progress, delete it from Run History. This error will come.

Error starting agent.
The Agent-1 job is in failure. Please manually change the job status to failed or succeeded to continue running jobs for this agent.

This error occurs when the latest job of the agent is in Failure status and the Continue on Failure job setting is not enabled. When a schedule triggers in this state, the job history shows: “Agent-1 job schedule failed to start because the job is in failure. You must manually change the job status to Failed or Succeeded.”

Steps to replicate:

Keep Continue on Failure disabled in the agent job settings.
Run the job and let it fail (e.g., set a success criteria that the run cannot meet).
Start the agent/job again without changing the job status. This error will come.

Error starting agent.
Agent Agent-1 is not allowed to run without a rate limit.

This error occurs when the organization has Rate Limit Required enabled and the agent has no rate limit applied.

Steps to replicate:

Edit the organization and enable Rate Limit Required.
Start an agent that does not have any rate limit applied. This error will come.

Error:
Agent Agent-1 schedules are not allowed to run without approval.

This error occurs when the organization has Agent Approval Required enabled and a schedule triggers for an agent that is not approved. The message is shown in the job/schedule status.

Steps to replicate:

Edit the organization and enable Agent Approval Required (existing agents are auto-approved).
Check in a new agent and do not approve it.
Add a schedule for this agent and let it trigger. This error will come.

Error starting agent.
Exceeded the allowed 2 concurrent sessions for agent Agent-1. 2 sessions are currently running.

This error occurs when a rate limit with a session limit and the prevent agent start on limit option is applied, and the running sessions already reach the limit.

Steps to replicate:

Create a rate limit with Session Limit = 2 and enable the option to prevent agent start when the limit is reached.
Apply the rate limit to an agent and start 2 sessions.
While they are running, start another session. This error will come.

Error starting agent.
Run already exist with the given runId 5 and sessionId=X

This error occurs when we start an agent with a custom Run ID and Session ID combination that has already been used for this agent.

Steps to replicate:

Start an agent with custom Run ID 5 and session ID “X” and let it complete.
Start the same agent again with Run ID 5 and session ID “X”. This error will come.

Job history could not be deleted
Unable to delete a job that is in progress. Manually set the job to failed or succeeded first.

This error occurs when we try to delete a job history entry that is In Progress or In Progress With Failure.

Steps to replicate:

Start an agent job.
While the job is in progress, go to Job History and delete it. This error will come.

Error:
Unable to delete schedule. You cannot delete schedule while the job is still in progress.

This error occurs when we try to delete a schedule while the agent's job is in progress.

Steps to replicate:

Add a schedule for an agent and let it start the job.
While the job is in progress, delete the schedule. This error will come.

Error saving job schedule.
You can't update time of once job schedule once it is in progress or completed

This error occurs when we try to change the time of an enabled Once schedule that has already run.

Steps to replicate:

Add a Once schedule for a deployed agent and let it run.
Edit the same schedule, change the time and save. This error will come.

Error saving job schedule.
Schedule with the same start time already exists.

This error occurs when we add a schedule for the same agent with the same schedule type, session, start time and time zone as an existing schedule.

Steps to replicate:

Add a schedule for an agent with a specific start time and time zone.
Add another schedule for the same agent with the same values and save. This error will come.

Error starting agent.
One or more schedules are currently running the Agent-1 job. You cannot run this job without schedules while schedules are trying to complete the job.

This error occurs when we manually start a job while a schedule is running the same job (and One Job Per Schedule is not enabled).

Steps to replicate:

Add a schedule for an agent and let it start the job.
While the scheduled job is in progress, start the agent job manually. This error will come.

Error restarting agent.
Agent Agent-1 not deployed to server 11.22.33.44. The ACC must know about the deployment to restart the agent.

This error occurs when we restart a run on a server/cluster from which the agent deployment has been removed.

Steps to replicate:

Run an agent on a server and let the run complete.
Remove the agent deployment from that server/cluster.
Go to Run History and restart the run. This error will come.

Error:
Agent run is queuing for a failed server ACCTest-11.22.33.44 that has been down for more than 30 minutes.

This error occurs when a run is queued for a server that has been down for more than 30 minutes; ACC sets the run to Failure and shows this message in Run History.

Steps to replicate:

Start an agent run on a server.
Stop the SE service on that server and keep it down for more than 30 minutes.
Check the run status in Run History. This error will come.

Error deleting server.
Error deleting server. Agents, config files or shared folders are deployed to this server.

This error occurs when we delete a server that still has deployments.

Steps to replicate:

Deploy an agent, config file or shared folder to a server.
Go to Servers and delete that server. This error will come.

Error deleting server.
Error deleting server. Agents are currently running on this server.

This error occurs when we delete a server while agents are running on it.

Steps to replicate:

Start an agent run on a server.
While the run is in progress, delete that server. This error will come.

Cluster Cluster-A couldn't be deleted.
This cluster cannot be deleted as it is associated with an organization. In order to delete it, please remove it from the organization first.

This error occurs when we delete a cluster that is assigned to an organization.

Steps to replicate:

Add a cluster (e.g., Cluster-A) to an organization.
Go to Clusters and delete that cluster. This error will come.

Cluster couldn't be saved.
Cluster name already exists.

This error occurs when we rename a cluster to a name that is already used by another cluster.

Steps to replicate:

Create two clusters, e.g., Cluster-A and Cluster-B.
Edit Cluster-B, rename it to Cluster-A and save. This error will come.

Directory could not be deleted.
Unable to delete directory because the directory is the root directory for one or more users. Please assign a different root directory for those users.

This error occurs when we delete a directory that is set as the root directory of a user.

Steps to replicate:

Set a directory as the root directory of a user.
Delete that directory. This error will come.

Directory could not be deleted.
Unable to delete sub-directories. Please delete all sub-directories before deleting this directory.

This error occurs when we delete a directory that has sub-directories.

Steps to replicate:

Create a directory and add a sub-directory to it.
Delete the parent directory. This error will come.

Agent config could not be deleted.
Error deleting config. The config file is deployed to one or more servers. You must delete the deployments first.

This error occurs when we delete an agent config file that is still deployed.

Steps to replicate:

Deploy a config file to a server/cluster.
Delete the config file without removing its deployment. This error will come.

Shared folder could not be deleted.
Error deleting shared folder. The shared folder is deployed to one or more servers. You must delete the deployments first.

This error occurs when we delete a shared folder that is still deployed.

Steps to replicate:

Deploy a shared folder to a server/cluster.
Delete the shared folder without removing its deployment. This error will come.

An error occurred whilst deleting the user.
You cannot delete the logged in user. Please login with a different user to delete this user.

This error occurs when an admin tries to delete their own user account.

Steps to replicate:

Log in to ACC as an admin and go to Users.
Delete your own user. This error will come.

Error adding access token.
Cannot add API keys for Server Admin and Super Admin users.

This error occurs when we try to create an API key for a Server Admin or Super Admin user.

Steps to replicate:

Go to API Keys for a Server Admin or Super Admin user.
Add a new API key. This error will come.

An error occurred disabling the organization Org-A.
You can't disable your organization yourself

This error occurs when a user tries to disable the organization they belong to.

Steps to replicate:

Log in with a user of organization “Org-A”.
Go to Organizations and disable Org-A. This error will come.

Rate limit could not be saved.
Rate limit already exists with this name. Please choose another name for the rate limit.

This error occurs when we save a rate limit with a name that already exists.

Steps to replicate:

Create a rate limit, e.g., RL-1.
Create another rate limit with the name RL-1 and save. This error will come.

Schedule label could not be saved.
Label already exist

This error occurs when we add a label with a name that already exists in the organization.

Steps to replicate:

Add a label, e.g., Daily.
Add another label with the name Daily in the same organization. This error will come.

Error
The file must be smaller than 300MB.

This error occurs when we upload an input file or a shared folder file larger than 300 MB.

Steps to replicate:

Open Input Files (or a shared folder) of an agent and click upload.
Select a file larger than 300 MB. This error will come.

Error
Invalid file type. Please upload .scgc files only.

This error occurs when we upload a connection file that does not have the .scgc extension.

Steps to replicate:

Go to Connections and click upload.
Select a file with any other extension (e.g., .txt). This error will come.

Error
Invalid Session. Current session should be less than total sessions.

This error occurs on the Run Agent or Schedule editor when the session ID entered is greater than the total number of sessions.

Steps to replicate:

Open Run Agent (or add a schedule) for an agent.
Set total sessions to 2 and enter session ID 3. This error will come.

```
Error
Invalid username or password
```

This error occurs on the login page when the username or password is wrong.

Steps to replicate:

Open the ACC login page.
Enter a valid username with a wrong password and click Login. This error will come.

Account does not exist
Microsoft account user@example.com does not exist in our system.

This warning occurs when we sign in with Microsoft (or Google) using an account that is not added as a user in ACC. For Google the message is “Google account user@example.com does not exist in our system.”

Steps to replicate:

Open the ACC login page and click Sign in with Microsoft (or Google).
Sign in with an account that is not added in ACC Users. This error will come.

Error
Two-factor authentication code is invalid. Please try again.

This error occurs when a wrong or expired code from the authenticator app is entered during two-factor authentication setup or login.

Steps to replicate:

Log in with a user that has two-factor authentication enabled.
Enter a wrong security code and submit. This error will come.

No Network
The server cannot be reached.

This error occurs on the login page when the browser cannot reach the ACC server.

Steps to replicate:

Open the ACC login page.
Stop the ACC service/website (or disconnect the network) and try to log in. This error will come.

User couldn't be saved.
The username already exists.

This error occurs when we add a user with a username that already exists.

Steps to replicate:

Go to Users and add a new user.
Enter the username of an existing user and save. This error will come.

Error
Username must match the user's email.

This error occurs when a user's authentication service is Microsoft or Google and the username is different from the email.

Steps to replicate:

Go to Users and add/edit a user.
Select Microsoft (or Google) as the authentication service, enter a username that is different from the email and save. This error will come.

Error
Your password must be atleast 6 character long.

This error occurs on the user editor, change password and reset password screens when the new password is shorter than 6 characters.

Steps to replicate:

Open Change Password (or add a user).
Enter a password with less than 6 characters and save. This error will come.

Error
Password and confirm password doesn't match.

This error occurs when the confirm password is different from the new password.

Steps to replicate:

Open Change Password (or add a user).
Enter different values in the password and confirm password fields and save. This error will come.

Organization could not be saved.
The organization name already exists.

This error occurs when we add an organization with a name that already exists.

Steps to replicate:

Go to Organizations and add a new organization.
Enter the name of an existing organization and save. This error will come.

Error
Session limit cannot be less than 1 or greater than 99.

This error occurs on the organization editor and rate limit editor when the session limit is outside 1–99.

Steps to replicate:

Add/edit an organization (or a rate limit with session limit enabled).
Enter 0 or 100 as the session limit and save. This error will come.

Directory could not be saved.
The directory name already exists.

This error occurs when we add or rename a directory with a name that already exists under the same parent directory.

Steps to replicate:

Create a directory, e.g., Dir-A.
Create another directory with the name Dir-A under the same parent and save. This error will come.

Error
Job/Run history retention period must be either blank or greater than 0

This error occurs on the directory editor when the retention period is 0 or negative. The same validation exists for Ticket retention period and Log retention period.

Steps to replicate:

Edit a directory.
Enter 0 in Job/Run history retention period and save. This error will come.

Error adding server.
Server name Server-1 already exists.

This error occurs when we add a server with a name that is already used by another server.

Steps to replicate:

Add a server with the name Server-1.
Add another server with the same name. This error will come.

Error adding server.
IP address 11.22.33.44 already exists.

This error occurs when we add a server with an IP address that is already added in ACC.

Steps to replicate:

Add a server with IP 11.22.33.44.
Add another server with the same IP address. This error will come.

Error
You must enter a port only in number.

This error occurs on the server editor when the port is not numeric. Similar validations exist for CPU, memory, disk and session thresholds.

Steps to replicate:

Go to Servers and add/edit a server.
Enter a non-numeric value (e.g., abc) in Port and save. This error will come.

Error removing agent from server.
The agent cannot be removed from the server because it's current running on that server. Please stop all running instances of the agent first.

This error occurs when we remove an agent from a server while an agent run is in progress on that server.

Steps to replicate:

Deploy an agent to a server and start a run.
While the run is in progress, remove the agent from the server. This error will come.

Error deleting server.
Error deactivating CG/SE on server 11.22.33.44:8005. Please deactivate manually.

This error occurs when we delete a server with deactivation and ACC cannot connect to the SE service on that server. The connection error details are added at the end of the message.

Steps to replicate:

Stop the SE service on a server that is added in ACC (with no deployments).
Delete the server from ACC with the deactivate option. This error will come.

Error starting agent.
Exceeded the allowed load of 100 [load type] for agent Agent-1.

This error occurs when the load counter of the rate limit applied to the agent has already reached the load limit.

Steps to replicate:

Create a rate limit with a small load limit and apply it to an agent.
Run the agent until the load counter reaches the limit (do not reset the load counter).
Start the agent again. This error will come.

Error
Domin cannot be empty when Domain Filter is enabled.

This error occurs on the rate limit editor when Domain Filter is enabled but no domain is entered.

Steps to replicate:

Add/edit a rate limit and enable Domain Filter.
Leave the domain empty and save. This error will come.

Error
Load limit minutes cannot be more than 59

This error occurs on the rate limit editor when the load limit minutes value is more than 59. Related validations: hours/minutes cannot be negative, cannot be decimal, and both cannot be less than 1.

Steps to replicate:

Add/edit a rate limit with load limit enabled.
Enter 60 in minutes and save. This error will come.

Error
Enable at least one success criteria out of Min Data Count, Max errors, Min Action Count or Min Export Rows

This error occurs on the job editor when success criteria is turned on but none of the criteria is enabled.

Steps to replicate:

Open the agent job settings and enable success criteria.
Keep Min Data Count, Max errors, Min Action Count and Min Export Rows all disabled and save. This error will come.

Error
Invalid Min Data Count. It should be between 0 to 100

This error occurs on the job editor when Min Data Count is a percentage and the value is outside 0–100. The same validation exists for Min Action Count, Min Export Rows Count and Max errors.

Steps to replicate:

Open the agent job settings and enable Min Data Count as a percentage.
Enter 150 and save. This error will come.

```
Error
You must enter a valid Run ID
```

This error occurs on the job editor when the Run ID is not a number.

Steps to replicate:

Open the agent job settings.
Enter a non-numeric Run ID (e.g., abc) and save. This error will come.

Error
Invalid range of sessions. start and end session should be less that total sessions.

This error occurs on Run Agent or the schedule editor when a session range is entered that goes beyond the total number of sessions.

Steps to replicate:

Open Run Agent (or add a schedule) for an agent.
Set total sessions to 3 and enter session range 2-5. This error will come.

Error
Please enter valid start date and time.

This error occurs on the schedule editor when the start date/time is in the past.

Steps to replicate:

Add a schedule for an agent.
Select a start date and time earlier than the current time and save. This error will come.

Error saving job schedule.
Invalid schedule. The CRON expression must contain 4 or 6 parts.

This error occurs when a schedule is saved with a CRON expression that does not have the required number of parts.

Steps to replicate:

Add a schedule for an agent using a custom CRON expression.
Enter an expression with the wrong number of parts (e.g., 0 0 *) and save. This error will come.

Error:
The following error(s) occurred whilst saving your changes: Proxy pool name already exists.

This error occurs when we rename a proxy pool to a name that already exists in the organization.

Steps to replicate:

Create two proxy pools, e.g., Pool-A and Pool-B.
Edit Pool-B, rename it to Pool-A and save. This error will come.

Error:
The below errors occurred whilst saving your changes Proxy provider pool name already exists.

This error occurs when we add a proxy provider pool with a name that already exists in the organization.

Steps to replicate:

Create a proxy provider pool, e.g., Provider-A.
Add another proxy provider pool with the name Provider-A and save. This error will come.

Error:
The below errors occurred whilst saving your changes: The config name Config-1 already exists in this directory

This error occurs when we add an agent config file with a name that already exists in the same directory.

Steps to replicate:

Add an agent config, e.g., Config-1, in a directory.
Add another agent config with the name Config-1 in the same directory and save. This error will come.

```
Error
You must enter a subject.
```

This error occurs when we create a new ticket without a subject.

Steps to replicate:

Go to Tickets and click New Ticket.
Select an agent, leave Subject empty and save. This error will come.

Error: 
Ticket already in closed status.

This error occurs when we set a ticket to Closed that is already closed.

Steps to replicate:

Open a ticket that is already closed.
Set the status to Closed again and update. This error will come.

Error
The file must be smaller than 100MB.

This error occurs when we attach a file larger than 100 MB to a ticket.

Steps to replicate:

Open a ticket and upload an attachment.
Select a file larger than 100 MB. This error will come.

Error
The file must be smaller than 1MB.

This error occurs when we upload a connection (.scgc) file larger than 1 MB.

Steps to replicate:

Go to Connections and click upload.
Select a .scgc file larger than 1 MB. This error will come.

```
Error
CSV content cannot be empty.
```

This error occurs on the input file editor when we save an input file without any CSV content. If the name is empty, the error is “Name cannot be empty.”

Steps to replicate:

Open Input Files of an agent and add/edit an input file.
Clear the CSV content and save. This error will come.

Error
Agent description cannot be empty.

This error occurs when we save an empty agent description. For agent versions the error is “Version description cannot be empty.”

Steps to replicate:

Open the agent description editor in Agent Repository.
Clear the description and save. This error will come.

```
Error
You must select a directory.
```

This error occurs on Move Agent when no target directory is selected.

Steps to replicate:

Select an agent in Agent Repository and click Move.
Click Move without selecting a directory. This error will come.

Error
Fatal application error: Error getting proxies. Error: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML><HEAD><TITLE>Not Found</TITLE></HEAD>
<BODY><h2>Not Found</h2><hr><p>HTTP Error 404. The requested resource is not found.</p></BODY></HTML>

This error is shown in the agent run log / Run History when an agent uses an ACC proxy pool and Sequentum Enterprise (SE) cannot get the proxy list from ACC. When the run starts, SE calls the ACC proxy API to get the proxies of the pool. If the ACC website is not available, IIS returns its generic “HTTP Error 404. The requested resource is not found.” page instead of the proxy list, and SE stops the run with this fatal error. The message itself comes from SE, not from the ACC code.

Why it comes during ACC installation/upgrade: while a new ACC build is being installed, the ACC website and app pool are stopped (or app_offline.htm is in the site folder), so nothing answers on the ACC URL. Any agent run that starts or loads its proxies in this window gets this 404. This is expected during the installation window and is not a problem with the new build.

If the error continues after the installation is complete, check the following, because an IIS 404 page means the request is not reaching the ACC site:

The ACC website and its app pool are started in IIS.
The site bindings (host name, port, SSL certificate) are the same as before the upgrade.
No app_offline.htm file is left in the ACC site folder.
The ACC URL configured on the SE servers matches the ACC site, and it opens in a browser from the SE server.

Steps to replicate:

Create a proxy pool in ACC (e.g., Pool-A) and set an agent to use this proxy pool.
Deploy the agent to a cluster.
On the ACC server, stop the ACC website in IIS (or place app_offline.htm in the site folder, as happens during an upgrade).
Start the agent on the SE server while the ACC site is stopped (for example, a run that is starting at the same moment the site is stopped). This error will come in the agent log.
Start the ACC website again and re-run the agent. The run gets the proxies and works.

Solution:

If the error time is inside the installation window, re-run the failed agents after the installation is complete.
Before installing a new ACC build, choose a time with no scheduled runs, or pause the schedules and enable them again after the installation.
If it still occurs after installation, fix the IIS site, app pool, bindings or SE’s ACC URL as listed above.