Error ACC-2503 - Data collection processing encountered a fatal error for Agent_Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } Agent is not succeed to discover with recent ecc queue showing the following error: "{\"data_collection\":{\"error_msg\":\"cmd_err: Cannot open a connection to WIN32OLE. Error type=WIN32OLERuntimeError; Error=failed to parse display name of moniker `winmgmts://'\\n HRESULT error code:0x80070422\\n The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.\\n\",\"error_backtrace\": Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } All releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #6e9db4; } a:visited { font-size: 12pt; color: #7057C7; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: 500px !important; width: auto; height: auto; } } The following steps can be used to troubleshoot and resolve the error:Cannot open a connection to WIN32OLE. Error type=WIN32OLERuntimeError; Error=failed to parse display name of moniker `winmgmts://'\\n HRESULT error code:0x80070422\\n The service cannot be started, either because it is disabled or because it has no enabled devices This is a Microsoft windows error and would best be resolved by a Microsoft Windows AdministratorYou can test running ACC checks directly on the host to help troubleshoot the issue: 1. Log onto the server and switch to the user that runs the ACC agent. 2. Navigate to the location C:/ProgramData/ServiceNow/agent-client-collector/cache/acc-f-commons/bin/ 3. Run the script with the arguments that the check shows it will run with in the ecc queue log:endpoint_discovery.rb --compact --select=data_collection,enhanced_inventory,file_systems,network_adapters,tcp_connections,storage_devices,running_processes You can try the steps in the following Microsoft post to resolve it: https://learn.microsoft.com/en-us/answers/questions/4034758/0x80070422-error The error code 0x80070422 means "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it". Press Win + R, type services.msc and click OK. This opens the Services MMC. Inspect (and fix if necessary) the startup type of the following services and try to start them for ACC only the following was needed to be updated to start AutomaticWindows Management Instrumentation [Automatic]