Unresolved issue while upgrading mid server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2022 10:08 PM
Getting the following error as "unresolved issue" after upgrading mid server from rome to tokyo:
WARNING: Skipping adding <midserverhostname>\<account name>: No mapping between account names and security IDs was done.
Issue source is 'MIDFilePermEnforcer'. Let me know if anyone has more details on this error?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2024 04:31 AM
Try this if you are using a service account that is domain joined.
WARNING: Skipping adding "Server"\"serviceAccount": "Server"\"serviceAccount": No mapping between account names and security IDs was done -> this error appears to come from EnforceFilePermission.psm1 when service account comes from domain. In line 68 of the code, script will add Server\ServiceAccount to whitelisting, which later on returns error during applying permissions due to lack of mapping for obvious reasons. There should be a mechanism that skips this step when service account is a domain account but there is not.
File location: (open as Admin in powershell Ise or similar)
##agent\bin\scripts\EnforceFilePermission.psm
This is the line to comment out
# #$whiteList.Add($computername + "\" + $username