SCOM Connectors failing with error "Connection test failed. Error running SCOM client. The system cannot execute the specified program."Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } SCOM Connectors (testing from em_connector_instance.LIST) fail with the below error fetched from the agent logs: 2022-10-11 04:50:38 (389) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 DEBUG: Copying E:\apps\ServiceNow\agent\bin\sw_wmi\bin\scom2007\SCOMClient.exe.config to E:\apps\ServiceNow\agent\extlib\\SCOMClientcd7aca2a1b6f2810d0a0744ead4bcbb1.exe.config 2022-10-11 04:50:38 (420) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 DEBUG: Copying E:\apps\ServiceNow\agent\bin\sw_wmi\bin\scom2012\SCOMClient2012.exe.config to E:\apps\ServiceNow\agent\extlib\\SCOMClient2012cd7aca2a1b6f2810d0a0744ead4bcbb1.exe.config 2022-10-11 04:50:38 (451) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 DEBUG: SCOM signature = 638010162950470000.f8d136c7-951d-4d57-80bb-fc87704abfd2 2022-10-11 04:50:38 (451) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 DEBUG: getLatestEvents called 2022-10-11 04:50:41 (186) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 DEBUG: SCOM Connector: running command: "E:\apps\ServiceNow\agent\extlib\SCOMClient2012cd7aca2a1b6f2810d0a0744ead4bcbb1.exe" false 15.63.0.153 AUTH\$momadminmsac **** 1000 638010162950470000 2022-10-11 04:50:43 (386) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 DEBUG: Debug: SCOM client command results is: 1, output is: 2022-10-11 04:50:43 (386) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 SEVERE *** ERROR *** Error running SCOM client: The system cannot execute the specified program. 2022-10-11 04:50:43 (386) Worker-Interactive:ConnectorProbe-3f60eed41b2ad110b3f37449cc4bcba4 SEVERE *** ERROR *** SCOM connector failed. The system cannot execute the specified program.Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } AllCause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Possibly due to corrupted configuration files in the MIDINSTALLEDDIRECTORY\ServiceNow\agent\bin\sw_wmi\bin\scom2012\SCOMClient2012.exe.config caused due to recent OS patching/security patching/mid servers upgrade. Validate if the .exe config files look good.Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } If the above .exe files do not look good please follow the below steps 1)Stop the mid-service 2)Copy config files from the properly working mid-server/connector to the non-working directory 3)start the mid-service and test the connector.