Mid server issue & mid server script files are missing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2022 09:39 PM - edited 10-17-2022 04:18 AM
We recently upgraded to Tokyo. After that mid servers are not working. The status is up but whenever I try to test the credentials I am getting an error.
Get-ChildItem : Cannot find path 'C:\ServiceNow\MIDserver\TST MID\agent\scripts\PowerShell\DiagnosticsUtil.psm1' because it does not exist. At line:1 char:1 + Get-ChildItem "C:\ServiceNow\MIDserver\TST MID\agent\scripts\PowerShe ... +
when I checked the mid-server config file for the above path. The PowerShell was missing. I stopped the mid-server service and put the file from one of the running mid servers from prod. When I restarted the service the folder was getting auto-deleted.
I have checked the mid-server script files. Are the files missing? How to get it back?
Please help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2022 09:43 PM
Hi,
Take a look at supportive kb -
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0549834
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657528
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0676313
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750860
Thanks,
Sagar Pagar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2022 01:08 AM
I have ecnounter the same issue. The powershell script is being erased after local server has been restarted.
Have you found a solution to that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2022 11:32 PM
For us, this happened because one of the tables was added to exclude the list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2022 11:45 PM
Thanks @pratiksha5 .
We also manage to solve the issue. The powershell script was added manually to MID Server file location and syncronisation rule has prevent to keep it in that file each time the local server was restarted.