Agent Client Collector Troubleshooting: A Practical Guide for ServiceNow Teams
Real-world fixes for common ACC issues including cache problems, service timeouts, and data collection errors that ServiceNow administrators encounter daily.
Real-world fixes for common ACC issues including cache problems, service timeouts, and data collection errors that ServiceNow administrators encounter daily.
- Cache corruption is the most common ACC issue and clearing it resolves most problems
- Service startup timeouts often indicate resource constraints on the host machine
- Always verify network connectivity and folder permissions before complex troubleshooting
- Phased rollouts prevent upgrade issues from affecting your entire estate
The Reality of ACC in Production Environments
If you have spent any time managing ServiceNow Discovery or Service Mapping, you know that the Agent Client Collector can be temperamental. One day everything works perfectly. The next morning, you arrive to find endpoints dropping off the radar without warning.
I have worked with dozens of enterprise clients who struggle with ACC issues, and the same problems keep appearing. This guide covers the fixes that actually work, based on what I have seen in the field.
ACC Architecture Overview
Common Issues and What Actually Fixes Them
Cache Corruption
This is probably the most frequent issue I encounter. The ACC cache becomes corrupted, and suddenly your data collection stops working properly.
Where to find the cache:
- Windows:
C:\ProgramData\ServiceNow\agent-client-collector\cache - Linux:
/var/cache/servicenow/agent-client-collector - Mac:
/Library/Caches/servicenow/agent-client-collector
The fix is straightforward. Stop the ACC service, delete the cache folder contents, and restart. The agent will rebuild everything on its own. I recommend scheduling a monthly cache clear for large deployments to prevent issues before they start.
Service Startup Timeouts
The Service Control Manager sometimes gives up before ACC finishes initialising. This happens more often on older hardware or virtual machines with limited resources.
You can extend the timeout threshold in the Windows registry, but honestly, the better solution is addressing the root cause. Check if your machine has enough memory allocated and whether the disk is under heavy load during startup.
Troubleshooting Workflow
Error Code ACC-2503
This one looks scary but usually has a simple cause. The error indicates a fatal problem with data collection processing, typically because the agent cannot write to its working directory.
Check folder permissions first. The service account running ACC needs full control over its installation and cache directories. I have seen this break after Windows updates change folder permissions silently.
Diagnostic Steps That Save Time
Before diving into complex troubleshooting, run through this checklist:
1. Verify network connectivity - Can the endpoint reach your ServiceNow instance? Firewalls and proxies cause more ACC problems than actual bugs.
2. Check the logs - ACC logs are surprisingly detailed. Look in the installation directory for recent entries.
3. Confirm agent version - Mismatched versions between the agent and your instance create strange behaviour. Upgrade stragglers when possible.
4. Test with a fresh install - If one endpoint works fine and another fails, comparing their configurations often reveals the issue immediately.
Upgrade Considerations
Upgrading ACC across hundreds or thousands of endpoints requires planning. I recommend a phased approach:
- Start with a pilot group of 20-30 machines
- Monitor for a week before expanding
- Keep rollback packages ready
- Document any custom configurations beforehand
The worst ACC upgrades I have seen happened when teams pushed changes to everyone simultaneously. One configuration issue affects your entire estate.
When to Escalate
Not every problem has a simple fix. Contact ServiceNow Support when you encounter:
- Repeated crashes with the same error code after clearing cache
- Issues that only appear with specific operating system versions
- Problems that started immediately after a platform upgrade
Collect logs and screenshots before raising a case. The support team works faster when they have good diagnostic information upfront.
ACC troubleshooting comes down to fundamentals: check connectivity, verify permissions, and clear the cache. Most issues I encounter in enterprise environments stem from one of these three areas. — Ali Qaiser, ServiceNow Architect