Breadcrumbs

List of SE Errors in ACC

This page lists errors that come from the exchange between Sequentum Enterprise (SE) and ACC and are shown in the ACC UI, the ACC log, the IIS log or the SE agent log. ACC validation errors are listed in List of Errors in ACC and backend exceptions in List of Exceptions in ACC.

SE run callbacks to ACC 

  1. Error:
Agent does not exist in ACC.

Returned with HTTP 500 when SE reports a run for an agent that ACC does not know. SE also reports runs of local agents (not started from ACC) when the ACC URL is set in SE Application Settings and the run environment matches the ACC environment.

Shown in: IIS log (500); SE agent log: 1-> Error posting ACC start notification. Error code: InternalServerError
API: POST /api/run/{agentRunId}/started, /completed, /deliverDataCheck

Steps to replicate:

  • On an agent server, set the ACC URL in SE Application Settings.

  • Create a new agent in SE that is not in ACC.

  • Run it locally in the Production environment. This error will come in the IIS log and the agent log.

Solution: ACC should return 404 with a clear message; SE should post to ACC only for runs started by ACC. This explains the 720 run-started failures from 10.5.2.15 on 24 Sep.


  1. HTTP 401:
Unauthorized

Returned when the calling server's IP is not a registered server of the organization and not in Authorized IPs. NAT, a load balancer or IPv6 can make ACC see a different IP. SE retries 20 times and then ends the run with exit code AccError.

Shown in: IIS log (401); SE agent log: Error posting ACC start notification. Error code: Unauthorized; ACC run stays Queued/Starting
API: POST /api/run/{agentRunId}/started, /completed, /deliverDataCheck, GET /api/proxy/pool/server

Steps to replicate:

  • Run an agent from a server whose IP is not added to the organization's servers (or put a proxy/NAT between the server and ACC).

  • Start the agent from ACC.

  • Check IIS for 401 and the run status in ACC. This error will come.

Solution: Read the client IP from X-Forwarded-For; return 403 with the IP in the message; SE should not retry 20 times on 401/403.


  1. Error:
ACC job run running on a different server {ip}. / ACC job run not found. / ACC job not found.

Returned in the run started response when ACC cannot match the run with the calling server's IP, or the job settings are missing. SE stops the run with exit code AccError.

Shown in: SE agent log: 6-> Error posting ACC start notification. Error: ...; ACC Run History shows the run failed or stuck
API: POST /api/run/{agentRunId}/started

Steps to replicate:

  • Use a server with two network cards, or both IPv4 and IPv6.

  • Start an agent from ACC on that server.

  • If ACC sees a different IP than the one stored for the run, this error will come.

Solution: Match the run by run ID only, update the server IP and log a warning when it differs.


  1. No error shown:
Run stays Queued in ACC while the agent is running

When saving the run start fails in ACC (for example a database deadlock or timeout), ACC still replies with success. SE continues, but ACC never sets the run to Running. Related ticket: ACC-1306.

Shown in: ACC Run History and Running Agents; the exception text is only in the ACC log (Information level)
API: POST /api/run/{agentRunId}/started

Steps to replicate:

  • Start many agents at the same time, or hold a lock on the AgentRun table in SSMS (BEGIN TRAN; UPDATE AgentRun ... without commit).

  • Start an agent from ACC.

  • The agent runs on the server but stays Queued in ACC.

Solution: Return 500 with the error so SE retries; log it at Error level.


  1. Error:
Error posting ACC completed notification.

When saving the run completion fails in ACC, ACC replies 200 with an empty body. SE cannot read it, retries 20 times (about 5 minutes) and logs this error. The run stays Running in ACC.

Shown in: SE agent log; ACC Run History shows Running after the agent finished
API: POST /api/run/{agentRunId}/completed

Steps to replicate:

  • Hold a lock on the AgentRun or AgentRunHistory table in SSMS as in the previous item.

  • Let a running agent finish.

  • ACC still shows Running and the SE log shows this error after 20 retries.

Solution: Return 500 with an error message; make completion idempotent so a retry after success returns success.


  1. Error:
Error posting ACC completed notification. Error code: ACC run not found.

SE waits only 10 seconds for the completed call, but ACC can take more than a minute (up to 76 s on 24 Sep). SE gives up and sends the call again; the second call finds the run already moved to history.

Shown in: SE agent log; IIS log: win32 status 64 (client disconnected) on run completed
API: POST /api/run/{agentRunId}/completed

Steps to replicate:

  • Start 20 or more agents that finish at about the same time.

  • Check IIS time-taken on run completed (over 10,000 ms).

  • Check the SE logs. This error will come.

Solution: Raise the SE timeout for completed to 60-120 s; ACC should return success if the run is already in history; speed up run completion.


  1. Error:
Error posting ACC delivery check notification. Error: ACC schedule not found. / ACC job history not found.

Returned when the job schedule or job history is deleted while the job runs. SE then skips data delivery and ACC shows no error.

Shown in: SE agent log; no delivery file and no error in ACC UI
API: POST /api/run/{agentRunId}/deliverDataCheck

Steps to replicate:

  • Start a scheduled job.

  • While it runs, delete the schedule or the job history in ACC.

  • Let the agent finish and check delivery. This error will come.

Solution: Deliver data by default, or fail the run with a message shown in ACC.


  1. HTTP 404:
Not Found on /api/job/{agentId}/deliveryComplete

SE posts the result of a data redelivery to this URL, but ACC has no such endpoint, so the redelivery result is never recorded.

Shown in: IIS log (404)
API: POST /api/job/{agentId}/deliveryComplete

Steps to replicate:

  • Trigger a data redelivery for a run.

  • Check the IIS log. This error will come.

Solution: Add the endpoint in ACC or remove the call from SE.


Other SE calls to ACC 

  1. Error:
Unable to update info for a non existing server {ip}

Logged when a server sends its load info from an IP that ACC does not know. ACC still replies 202, so SE never knows. The server shows Offline or old values and its run queue is not processed.

Shown in: ACC application log; Servers page
API: POST /api/server/updateServerInfo

Steps to replicate:

  • Change an agent server's IP (or route it through NAT).

  • Wait a minute.

  • Check the ACC log and the Servers page. This error will come.

Solution: Return 404 so SE logs Error sending server info to ACC; show a warning for unknown servers in ACC.


  1. Error:
The proxy pool {name} was not found. / The proxy path does not contain an organization. / Unauthorized

Returned when an agent loads an ACC proxy pool with a wrong name or path. When the agent ID is not sent, ACC also requires the server IP to be in Authorized IPs, even for registered servers. A missing path gives HTTP 500.

Shown in: IIS log (404 / 401 / 500); agent runs without proxies
API: GET /api/proxy/pool/server

Steps to replicate:

  • In an agent, use an ACC proxy pool with a wrong name, or a path without the organization, and run it on a server.

  • Or call GET /api/proxy/pool/server without agentId from a registered server that is not in Authorized IPs.

  • This error will come.

Solution: Allow registered servers without agentId; return 400 for a bad path. Matches the 159 proxy-pool 401s on 24 Sep.


  1. HTTP 500:
Internal Server Error on job start without a login

Job start without a user token fails with an unhandled error (null user) instead of 401 Unauthorized.

Shown in: IIS log (500)
API: POST /api/job/{agentId}/start

Steps to replicate:

  • In Postman, call POST /api/job/{agentId}/start without an Authorization header.

  • This error will come.

Solution: Require authorization on the endpoint and return 401. Explains part of the 155 job-start 500s on 24 Sep.


  1. Error:
The username or password is incorrect.

Returned with HTTP 500 (instead of 401) for a wrong password. Scripts on agent servers that log in with old credentials cause it.

Shown in: IIS log (500)
API: POST /api/auth/login

Steps to replicate:

  • In Postman, call POST /api/auth/login with a wrong password.

  • This error will come with HTTP 500.

Solution: Return 401; find the script on 10.6.2.27 / 10.5.2.19 using old credentials (106 of 106 logins failed on 24 Sep).


ACC calls to the SE agent service 

  1. Error:
Error starting agent {agent} on server {server}. Server error: The agent {agent} is already running with session {session}.

Shown when ACC starts an agent on a server and SE refuses. Other SE reasons in the same message: The key does not have access to run the agent {agent}; The agent {agent} requires full scripting access.; This agent does not support sessions...; Invalid performance session ID ...

Shown in: ACC UI error toast; run marked failed; ACC log
API: POST /api/job/{agentId}/start, POST /api/agent/{agentId}/cluster/start

Steps to replicate:

  • Start an agent from SE desktop on the server.

  • Start the same agent and session from ACC.

  • This error will come. (For the key error, change the server key in SE and start from ACC.)

Solution: Pre-check in ACC (session already running, scripting level) and show the SE reason without the technical wrapper.


  1. Error:
Error stopping agent run on server {server}. ... Agent {agent} with session {session} is not running.

Shown when ACC stops a run that SE no longer has. A similar SE reason: The agent run is not available on this server. It may have been overwritten or removed.

Shown in: ACC UI error toast; run stays Running
API: POST /api/run/agent/{agentId}/stop

Steps to replicate:

  • Start a run from ACC.

  • End the agent process on the server (Task Manager).

  • Click Stop in ACC. This error will come.

Solution: Treat not running / not available as already stopped and close the run in ACC.


  1. Error:
Error accessing agent run on server {server}. An empty response was received / An invalid response was received

Shown when ACC refreshes a run and the SE server returns nothing usable, for example after the agent was redeployed during the run.

Shown in: ACC Run History refresh; ACC log
API: GET /api/run/{agentRunId}/refresh

Steps to replicate:

  • Start a run from ACC.

  • Redeploy the agent on that server while it runs.

  • Click Refresh on the run in ACC. This error will come.

Solution: Fail the run with a clear reason after several failed refreshes.


  1. Error:
Unable to delete session on server {server}. Cannot close a session with a running agent. Stop the agent first.

Shown when a session is deleted in ACC while the agent is still running in it.

Shown in: ACC UI error toast

Steps to replicate:

  • Run an agent with a session.

  • Delete that session in ACC while it runs.

  • This error will come.

Solution: Disable the delete action in ACC while the session is running.


SE run failure messages shown in ACC 

  1. Run message:
Agent did not complete within maximum allowed time span of {time}.

SE stopped the run because it passed the agent's maximum run time.

Shown in: ACC Run History status message; failure ticket/email

Steps to replicate:

  • Set the agent's maximum run time to 1 minute.

  • Run a longer agent from ACC.

  • This message will show in Run History.

Solution: Expected behaviour; check the message and the ticket.


  1. Run message:
The agent has not collected data for {n} minutes. Stopping agent.

SE stopped the run because no new data was collected within the set time.

Shown in: ACC Run History status message; failure ticket/email

Steps to replicate:

  • Set a low no-data timeout on the agent.

  • Run an agent that waits on a slow page.

  • This message will show in Run History.

Solution: Expected behaviour; check the message and the ticket.


  1. Run message:
Invalid existing data. Cannot continue agent.

SE cannot continue a run because the saved data does not match the agent (also: Unable to continue data extraction. The agent has changed and requires a different internal data structure. You must restart the agent.).

Shown in: ACC Run History status message

Steps to replicate:

  • Run an agent and stop it.

  • Change the agent's data structure and redeploy.

  • Run it again with Continue. This message will show.

Solution: Show a hint in ACC to use Restart.


  1. Run message:
Invalid license. ... / Error starting agent. Check log file. Exit code: {code} / Timeout waiting for agent process to start

SE could not start the agent on the server (licence problem, process failure or start timeout).

Shown in: ACC Run History status message; failure ticket

Steps to replicate:

  • Use an expired SE licence on a test server, or end the agent process during start.

  • Start an agent from ACC on that server.

  • This message will show.

Solution: Show a server-level alert in ACC for licence errors.


  1. Run message:
The web browsers terminated unexpectedly... Restarting web browsers.

SE restarted its browsers during the run.

Shown in: SE agent log; ACC run log

Steps to replicate:

  • Start a run from ACC.

  • End the browser processes on the server during the run.

  • This message will show and the run should continue.

Solution: Expected behaviour; check that the run continues.


  1. Run message:
Agent exceeded session limit of {n} for domain {domain} / Agent exceeded load limit of {n}

ACC stopped the run because a rate limit was reached.

Shown in: ACC Run History stop message

Steps to replicate:

  • Set a rate limit with session limit 1.

  • Start two sessions of an agent that uses it.

  • This message will show.

Solution: Expected behaviour; check the message.


Logging and configuration 

  1. Log issue:
ACC-1011 |RemoveMe Debug Log| Sending start request to Server ... URL: ...key=...

On every run start ACC writes the full SE agent-service URL to its log, including the server key.

Shown in: ACC application log

Steps to replicate:

  • Start any agent from ACC.

  • Open the ACC log and search for ACC-1011. The server key is visible.

Solution: Remove this log line or mask the key.


  1. Log issue:
DEBUG_LOG | The Request '/api/run/agentRunId/started' ... / ACC-774: Remove me

Debug traces for every run started and completed call are written at Information level, which makes the ACC log very large and hides real errors.

Shown in: ACC application log

Steps to replicate:

  • Start any agent from ACC and let it finish.

  • Open the ACC log and search for DEBUG_LOG.

Solution: Move these lines to Debug level or remove them.


  1. HTTP 404:
Not Found on SE server calls when ACC is hosted under a sub-path

SE runtime calls (server info, proxy pool, latest production version) use only the host of the ACC URL and drop any path after it.

Shown in: IIS log (404); server shows Offline; proxies not loaded
API: POST /api/server/updateServerInfo, GET /api/proxy/pool/server, GET /api/agent/{agentId}/server/latestProductionVersion

Steps to replicate:

  • Host ACC under a sub-path, for example https://host/acc2/.

  • Connect a server with that ACC URL.

  • Check the IIS log. This error will come.

Solution: Keep the full base path from the ACC URL in SE.