Logged in user 'mid.server' does not match configured user

[matt_a]

We recently cloned our live instance back to our dev environment.

Now, when I go to the mid server, I get an error message saying : Logged in user 'mid.server' does not match configured user

Im thinking that although the mid server didnt get cloned, the mid.server user did.

But this is a clone from live, so the mid.server user has the correct roles and the config.xml is the same.

The field on the mid server record is a string, so dont see then how the clone could have affected it?

Could anyone point me in the right direction? This isnt a major issue, just impacting me testing some orchestration processes in dev.

Thanks

[ServiceNowSteve]

On your mid server go to the agent folder and then right click and edit the config file. Look for the username and password strings there and manually update them to match the user you have authenticating to the mid server. You know it worked if after you save the credentials it encrypts the password.

[matt_a]

The username in the config is the same. Could it therefore be the password? IF so, should I stop the service prior to updating the password?

[ServiceNowSteve · Accepted solution]

yes stop the service, change the password in the file to match the user in ServiceNow then restart the service. It should encrypt the password at that point.

[matt_a]

Hi Steve,

I have tried this but no joy. I have also tried to re-validate but now in a constant state of Down and Validating