ACC Agent Showing Disconnected or Down

SRSkaggs
Tera Expert

Please see attached image, I have been troubleshooting a while and trying to figure out why the agents are still showing disconnected or down after upgrading instance to DC.

 

acc issue.jpg

 

1 ACCEPTED SOLUTION

SRSkaggs
Tera Expert

We ended up reaching out to Now Support and they provided us with a solution.

 

Here is their response: 

 

The Table API Access Control is denying the request by the MID Server to fetch the 'AgentKeepAliveTransformer' MID Server Script Include (ecc_agent_script_include). This ACL is inactive in the latest OOTB version as well as in ptvedev which is why the issue did not exhibit there.

 

Solution Proposed:You can either:
1) Revert the Table API Access Control to the latest OOTB version (which is inactive)
2) Add the mid_server role to the Table API Access Control

Next Steps: Retest with this ACL no longer preventing retrieval of the required MID Server Script Include by restarting the MID Servers to initiate a file sync for the 'AgentKeepAliveTransformer' MID Script Include.

 

This resolved the issue and the ACC agents are all now in a up state

 

 

View solution in original post

7 REPLIES 7

SK Chand Basha
Giga Sage

Hi @SRSkaggs 

 

Refer this thread it might be helpful

 

https://www.servicenow.com/community/itom-forum/what-is-the-current-best-practice-for-acc-agent-or-s...

 

Mark it Helpful and Accept Solution!! If this helps you to understand

I appreciate it, even though good information, it did not have anything that is helpful to my issue.

Hank Woo
Tera Guru

Hi @SRSkaggs 

 

In my case, after update DC, websocket endpoint url has been changed.

ws://*** to wss://***.

So I changed endpoint url then accs are being connected.

You can check this information in your mid server.

Please check your mid server's log.

Web sockets are showing as the correct one stated in your message, no change to the ACC agent status