After installing or upgrading the MID Server host to use Oracle JRE version 1.8.0_231, the MID Server is unable to run some programs:

  • powershell.exe - The Powershell probes that run for Windows Discovery will fail.  There are no responses provided by the probes when running Discovery under these conditions. There are no responses from WMI calls.
  • SCOMClient.exe - The Event Management SCOM Connector cannot be started.

Oracle Java 8u231 introduced some argument restrictions with commands that are executed through Runtime.exec or ProcessBuilder, which the MID Server uses for launching some PowerShell commands.

Steps to Reproduce


  1. Run Discovery on a Windows Machine.
  2. "Windows - Classify" probe will return error:

    & { [Console]::OutputEncoding = [Text.UTF8Encoding]::UTF8; Write-Output SNC_PowerShell_PID=9172; & 'scripts\\PowerShell\\PSScript.ps1' -computer '' -script 'Drive:\\Folder\\agent\\scripts\\PowerShell\\script_name.ps1' -useCred False -ismid True -isDiscovery True -debug False -logInfo False -skipTest False; exit }

  3. "Windows - Classify" probe does not behave as expected and the discovery stops with no details collected. No subsequent probes/patterns will be launched. The MID Server agent log shows something like:
    Worker-Interactive:MultiProbe-ab9731481b458094b9f686ecdc4bcb95 Worker starting: Powershell source: <IP_ADDRESS>
    Worker-Interactive:MultiProbe-ab9731481b458094b9f686ecdc4bcb95 DEBUG: Inside Script Runner -- Begining @@@@@@@@@@@@@@@@@@@: 06:44:13
    Worker-Interactive:MultiProbe-e39731481b458094b9f686ecdc4bcb97 DEBUG: after running the powershell command, ElapsedTime: 06:44:25
    Worker-Interactive:MultiProbe-e39731481b458094b9f686ecdc4bcb97 DEBUG: Inside Script Runner - Ending Time: 06:44:25
    Worker-Interactive:MultiProbe-e39731481b458094b9f686ecdc4bcb97 Worker completed: WMIRunner source: <IP_ADDRESS> time: 0:00:13.540


  1. Start an instance of the SCOM Connector
  2. You will see the following error:

    Error running SCOM client: '\"<mid server folder>\agent\extlib\SCOMClient2012<a sys_id>.exe\"' is not recognized as an internal or external command, operable program or batch file.SCOM connector failed. '\"<mid server folder> \agent\extlib\SCOMClient2012<a sys_id> .exe\"' is not recognized as an internal or external command, operable program or batch file

  3. Downgrade to a pre-231 version e.g. Oracle JRE 1.8.0_221. Run same Discovery again, everything works as expected.

Expected behavior:
Upgrading to the latest version of Oracle JRE, that may have been recommended due to vulnerability management, and is allowed in our documentation, should not break any MID Server functionality.

Actual behavior:
By installing the new JRE release, Discovery and Event Management does not work as expected.


This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.

The workaround is to set the Java system property jdk.lang.Process.allowAmbiguousCommands to true:

  1. Log in to the MID Server Host, and find the install folder. (The MID Server record in the instance has fields for both Host Name and Home Directory)
  2. Open the wrapper-override.conf file in a text editor - ./agent/conf/wrapper-override.conf
  3. Add the following line at the end, and save:
  1. Restart the MID server service.

Related Problem: PRB1372715

Seen In

SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - SIG Questionnaire - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - CarbonBlack Integration - New York 2019 Q3
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Configuration Compliance - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Intended Fix Version


Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-06-29 07:31:26