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.
Getting SEVERE *** ERROR *** Failed while executing script<random character sequence>.PS1 (Access denied) when trying to execute Custom Powershell Script - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Getting SEVERE *** ERROR *** Failed while executing script<random character sequence>.PS1 (Access denied) when trying to execute Custom Powershell Script
KB0780904

Getting SEVERE *** ERROR *** Failed while executing script<random character sequence>.PS1 (Access denied) when trying to execute Custom Powershell Script


3167 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

When running a Custom Powershell script using a Custom Orchestration Activity, it is generating the following error below.

Getting SEVERE *** ERROR *** Failed while executing script<random character sequence>.PS1 (Access denied)

Cause

This issue could be due to Permission or Credentials related.

Resolution

  1. Check whether the service account running the MID server service has permission to run the script in windows\temp.
  2. Test couple of simple PowerShell command like "ls"
  3. Check to see if there is a Credential tag on the Custom Activity and make sure that the same tag exists on the credential table.
  4. Test the credential with the target IP to make sure that the credentials works.
  5. On this particular issue, the error was generating due to a broken credential record.

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.