Issue
I had been reviewing the discovery logs and found Missing Classification Information warnings.
I also noticed in the ECC Queue that discovery stopped at the WMI: Classify phase 2.
Initially I thought it was a credential issue, but when I opened the WMI: Classify input XML I found the following:
& { [Console]::OutputEncoding = [Text.UTF8Encoding]::UTF8; Write-Output SNC_PowerShell_PID=3452; & 'scripts\PowerShell\PSScript.ps1' -computer 'x.x.x.x' -script 'C:\Windows\TEMP\GenerateWMIScriptPS1_WMI_FetchData.8364804381326014946.PS1' -useCred True -ismid False -isDiscovery True -debug False -logInfo False -skipTest False; exit }
The Classify probe wasn’t getting a response back.
Root Cause
During the routine patching of our MID servers, Java was updated to version 8 release 231 (build 1.8.0_231-b11/8.0.2310.11).
The WMI probes began failing after this Oracle Java update. Oracle Java 8u231 introduced Runetime.exe and ProcessBuilder argument restrictions that the MID server uses for running some PowerShell commands. More details for Java 8u231 at URL: JDK 8u231 Update Release Notes
Work Around
The Java system property jdk.lang.Process.allowAmbiguousCommands can be set to true to resolve the issue. On the MID Server, open the wrapper-override.conf file (/agent/conf/wrapper-override.conf) and add the following line at the end of the file:
wrapper.java.additional.3=-Djdk.lang.Process.allowAmbiguousCommands=true
Restart the ServiceNow MID server service.
Additional Information
More details can be found in KB article KB0784442: MID server running Oracle JRE version 8 release 231 can't start some applications - Discovery Powers....
