Mid server user authentication issue

[maheshkhatal]

Hello All,

         I had mid server setup on my local machine. Recently, after my laptop was upgraded I had to re-install everything.

I have followed all steps including creating mid server user with mid_server role but still getting following error in the log file 

2023-10-27T14:11:51.204+0530 WARN  (StartupSequencer) [UserConfigTest:38] Could not authenticate user 'mid.server' on the ServiceNow instance
2023-10-27T14:11:51.204+0530 ERROR (StartupSequencer) [StartupSequencer:730] test failure
java.lang.IllegalStateException: User: mid.server cannot be authenticated. User does not exist, or missing the proper roles. If you have deleted or changed the MID server keystore, and config.xml mid.instance.password value is encrypted, you may need to change this value to plain text (during MID startup, password is re-encrypted using current keystore and written back to mid.instance.password).
	at com.service_now.mid.services.StartupSequencer.runTests(StartupSequencer.java:668)
	at com.service_now.mid.services.StartupSequencer.startupSequencerRunnable(StartupSequencer.java:727)
	at java.base/java.lang.Thread.run(Thread.java:829)

 I am trying this with another instance. But still getting the same error.

One thing that I noticed is that some old password is getting encrypted in the config.xml file despite putting the current password associated with midserver user.  I know this is associated with key store file but unable to figure out how to get rid off this.

Thank you,

Mahesh.

[PavanBV]

Have you tried creating a new user again and reinstall using a new package? Ensure there are no proxies in between SN and MID Server

[MarkM1172412930]

Just curious if you solved this. I am building some new MID servers to replace old ones and the new ones get this error. The old ones are still running using the same credentials I am attempting to use on the MID Servers so I know the password is not the issue.