
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2019 03:38 AM
Hi Experts,
I am getting the below error in one of the MIdserver. Has anyone encountered with this error before.
How can i resolve this.
Error encountered when invoking PowerShell, the result from running '"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -noninteractive -nologo -noprofile -command "$ver = if (Test-Path Variable:\PSVersionTable) { $PSVersionTable.PSVersion } else { (get-host).Version }; 'full_version:' + $ver.ToString() + ', major_version:' + $ver.Major"' is
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2019 10:37 PM
Please note that this error can be caused by running a powershell script that is not signed on an environment that requires those scripts to be signed. There are some powershell scripts used by Orchestration that is currently not signed.
This is a known issue and has been raised with ServiceNow as PRB1349797. For more information, please see KB0752093

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2019 05:21 AM
Is there any text beyond what you have given here? You are showing the command, but not the error. That said, have you looked at the PowerShell troubleshooting guide?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2019 09:28 PM
hi,
Have you got this issue resolved, i am facing similar issue with my MID and not getting solution to fix. Please let me know the solution if you have got.
Regards
Digvijay

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2019 01:29 AM
HI
I haven't received the solution for this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2019 08:43 PM
Hi,
I also faced this issue it got fixed once I revalidated the mid server,
Regards
Harshal