Unresolved issue while upgrading mid server

[Justin Jacob]

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?

[Pat Quinn]

We are experiencing the same issue as FYL. MID server is Up and Validated, but we get the warning:

WARNING: Skipping adding <midserverhostname>\<account name>: <midserverhostname>\<account name>: No mapping between account names and security IDs was done.

We are also using a domain service account to run the MID server service, so we expected the warning to be for <domain>\<account name> , but instead it is for <midserverhostname>\<account name> , a local account which does not exist.

We ran gpupdate /force in an admin CMD prompt and then invalidated and re-validated the MID server and the warning appears to have cleared? We're still monitoring to see if it comes back.

[Brian O_Donnell]

I have had the same experience. Did the issue come back for you or did it remain resolved?

[Pat Quinn]

It did remain resolved, and we actually had the issue occur again with a new MID server install this week and the same steps (running gpupdate /force in an admin Powershell session, then invalidating and re-validating the MID server) did resolve the issue and clear the warning!

[HeyMarkWarmack]

Thanks for posting this.  Easy fix. 

My steps:

Changed username/password to make unique (WashDC requirement), enable started service (disabled and stopped to change the config.xml username/password), got the new MIDFilePermEnforcer error, did gpupdate /force, invalidated and then re-validated from within MID Server, refresh MID Server page for about 2 to 3 minutes, all green.

Thanks!

All Unresolved Errors went away.

[LaoJuntasa]

I think that you may want to bring this one to the shop man. As part of the upgrade process, the MID Server needs to remove and replace certain files. If for some reason one of those files cannot be deleted, the MID Server upgrade fails. Unfortunately, at the time of the Istanbul release, there is no way to recover and proceed with the upgrade. If you have not been able to gain access to the agent log following this troubleshooting guide, contact your network or system administrator. The MID Server host machine might be powered off or inadvertently off-network.