MID server auto upgrade issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2022 07:52 AM
Hello all,
During servicenow upgrades MID server failed to upgrade stating "Interactive authentication required" error because of missing permission(s)." in the wrapper log. Concerned with this, is my query below
In order to access MID server host from servicenow mid_server role is necessary similarly is there any necessary role that a user needs to have at the host to connect with servicenow.
Thanks in advance
- Labels:
-
MID Server

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2022 08:01 AM
Hi @Mahesh
Check resolution for this in HI portal, you will have to login:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0997225
Feel free to mark correct, if your issue has been resolved, so it ends up in solved queue.
Will be helpful for others looking for the similar query.
Aman Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2024 01:42 AM
Thank you @Per Kristian1 for the solution.
Hi @Mahesh23,
Please check if Kristian's approach works.
In parallel you can also check with the IT team. This might be the issue with Power Shell. Like we have issues with WMI connectivity in case of Win machines. IT team will troubleshoot with some commands and will resolve this by giving necessary permissions required.
Thank you,
Rishikesh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2022 01:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2023 09:54 AM
What is the actual resolution to this problem? My unix team is scratching their head reading this and wondering what the app is expecting. We have a sudoers file configured with NOPASSWD to use /usr/bin/systemctl start <service name>.service as root from our service account.