
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 06:27 AM
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
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 07:25 AM
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2019 05:07 AM
reset the password again and this time it worked!
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 08:02 AM
Hi,
what user you have logged in.
i think you you have logged with other user like admin..
so it will give the error,(no issue with that becouse first time it checks the user is same or not)
once impersonate with mid user and check mid server is there or not in application navigator
validate it and use it.
thanks
varsha