ACC Admin Workspace - Diagnostic Tests - Product Knowledge

ACC Admin Workspace - Diagnostic Tests The Agent Client Collector (ACC) agent includes a self-test or diagnostic framework that validates configuration and permissions. Errors indicate the agent cannot proceed with data collection due to configuration issues, missing permissions, or environmental problems.

As part of the June 2026 store app release of ACC Admin Workspace (bundled with the ITOM Infra Services Workspace store app), diagnostics may be triggered and viewed from within the agent record of the workspace.

What are diagnostic tests? The ACC agent includes a self-test framework that validates configuration, permissions, and dependencies required for data collection. These tests catch data collection failures and can catch problems early — before they surface as silent data gaps.

When do the tests run? Diagnostic tests run on demand — either when you trigger a diagnostic check from the ACC Admin Workspace, or when running manual diagnostic commands against the agent. They do not run automatically during startup or normal operation.

What do the results mean? If all tests pass, the agent's configuration and environment are healthy for data collection. If any test fails, the agent logs a specific error code (ACC-42XX) so you can identify exactly which check failed and what needs attention.

Diagnostic test error summary Error Code Test Name What It Checks What to Look At ACC-4201 Allowlist Validation Whether check-allow-list.json is valid JSON with correct syntax JSON syntax errors, file permissions, unescaped backslashes (especially on Windows) ACC-4202 Cache Directory Creation Whether the agent can create its cache subdirectories for plugins, assets, and checks Disk space, directory ownership, SELinux/AppArmor policies ACC-4203 MID Server Authentication Whether a valid API key is configured in acc.yml Missing or empty api-key field, missing agent-key-id after first startup ACC-4204 MID Server Connection Config Whether backend-url in acc.yml contains properly formatted WebSocket URLs URL format (must use wss:// or ws:// with /ws/events path), YAML syntax ACC-4205 MID Server Connectivity Whether the agent can actually reach the MID Server MID Server status, firewall rules, DNS resolution, TLS certificates ACC-4206 OSQuery Availability Whether the osqueryi binary is present and executable Plugin cache contents, file permissions, architecture mismatch ACC-4207 PAC File Whether the configured proxy auto-config file is reachable and valid PAC URL accessibility, JavaScript syntax in the PAC file ACC-4208 PowerShell Version (Windows) Whether PowerShell 5.1+ is installed PowerShell version; upgrade via Windows Management Framework 5.1 if needed ACC-4209 Ruby Script Execution Whether the bundled Ruby interpreter is present and functional Bundled Ruby binary existence and permissions; reinstall agent if missing ACC-4210 Sudo SS Access (Linux) Whether the service account can run ss with sudo for network data collection sudoers configuration for the servicenow user, !requiretty setting ACC-4211 WMI Permissions (Windows) Whether the service account has WMI query access Membership in "Performance Monitor Users" and "Distributed COM Users" groups, WMI namespace security

Next steps when a self-test fails 1. Check the agent log for the specific ACC-42XX error code. 2. Review the "What to Look At" column above for that code. 3. Fix the underlying issue and restart the agent. 4. Re-run the diagnostic check to confirm the test passes.