MIDFilePermEnforcer issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2020 09:25 PM
Hello, I am trying to install Mid server in windows system. Mid server connection and configuration is successful, but when I open up mid server list page it is showing empty. Please help!!
Getting this Mid server issue:
An unexpected error occurred: Write-Warning : The Win32 internal error "No process is on the other end of
the pipe" 0xE9 occurred while getting console output buffer information.
Contact Microsoft Customer Support Services.
At C:\win_demo\agent\bin\scripts\EnforceFilePermissions.psm1:92 char:9
+ Write-Warning "Could not disable file permission inheritance ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (:) [Write-Warning],
HostException
+ FullyQualifiedErrorId :
GetConsoleScreenBufferInfo,Microsoft.PowerShell.Commands.WriteWarningCommand

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-22-2020 05:16 AM
You had to reinstall, dang. I have 7 with the issue on one host.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2024 12:53 AM
Is this issue resolved,i am facing same issue.
"C:\MidServer\mid.tokyo-07-08-2022__patch9-hotfix2b-07-19-2023_08-01-2023_1829.windows.x86-64\agent\bin\scripts\EnforceFilePermissions.psm1 is not digitally signed. You cannot run this script on the current system"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2024 02:38 AM
Check for certificates. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863673
If you click on browser in the mid server machine where you have entered the servicenow URL. You will see additional certificates that you might need to add.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-09-2024 03:20 AM
Issue got resolved by digitally signing the PowerShell script and uploading it on servicenow instance under mid server script file