Unresolved issue while upgrading mid server

Justin Jacob
Tera Contributor

‎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?

0 Helpfuls
  • 3,447 Views
10 REPLIES 10

RRolling
Tera Guru

‎11-09-2022 02:58 PM

Justin,

 

Last Friday we did the same upgrade and I'm seeing the same warnings on my mid servers. Have you been able to resolve this? If so, can you share your solution?

 

Robert

0 Helpfuls

Justin Jacob
Tera Contributor
In response to RRolling

‎11-09-2022 09:44 PM

Hi Robert,

 

The account name appearing in the 'Warning' message is the account with which the mid server service would be running. You can verify this once in your environment.

 

Also, the warning message got resolved on its own with the Tokyo patch 3 that got installed on the instances.

0 Helpfuls

Todd Berry
Tera Contributor
In response to Justin Jacob

‎11-11-2022 05:35 AM

Do you have a KB article on this fix for Tokyo patch 3?  We are on patch 2 and i'm seeing this issue on all our mid servers and they are not unable to be validated.  I can't find anything.

0 Helpfuls

FYL
Mega Sage

‎12-12-2022 08:37 PM - edited ‎12-12-2022 08:38 PM

I am also encountering the same warning on Tokyo Patch 3. Not sure if it is this due to this particular release though as it is a new instance. MID Server is still UP and Validated though.

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

The service account that we are using to run the mid server service is a domain account and should not be be <midserverhostname>\<account name> but instead should be <domain>\<account name> 


0 Helpfuls