Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Discovery failing on Error: Missing expression after unary operator - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Discovery failing on Error: Missing expression after unary operator
KB0783025

Discovery failing on Error: Missing expression after unary operator


2447 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Discovery failing on Error: Missing expression after unary operator

When I run discovery I notice the error: 
"Error: Missing expression after unary operator '-'.At line:1 char:2+ -E <<<< xecutionPolicy ByPass -NonInteractive -WindowStyle Hidden -command &"

Cause

The error happens when running the command '-ExecutionPolicy ByPass -NonInteractive -WindowStyle Hidden' so you can test this by running the following command on the affected MID Server and check the output text file to see if it has the same error or not.

# powershell -ExecutionPolicy ByPass -NonInteractive -WindowStyle Hidden > C:\SampleFolder\output.txt

Observe the Powershell version that your MID Server is using?

PowerShell version 1.0 running on remote mid server or remote host.

Minimum pre-requisite for PowerShell is v2.0

Resolution

Ask if PowerShell can be upgraded to 2.0 or higher to satisfy Discovery requirements.

Confirm after upgrade PowerShell 2.0 or higher resolved the issue.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.