Windows MID server setup issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2017 09:53 AM
Hi Guys
Im trying to setup a new mid server in my instance but ive run into an issue I carnt seem to get round.
When I try and test the connection I get the below error
Error - User cannot be authenticated or is 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).
I have download the MID software straight from Servicenow and followed the same procedure I have countless time before but ive never encountered this error before.
What ive tried
- User name and password has been check
- User permission has been checked
- ive tried installed on bot 😧 and C:
- ive checked to make sure nothing is enryted
Any ideas ?
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2017 12:03 PM
open config.xml in notepad and update password and then save file.
you can run windows service from command prompt and check for any errors on console.
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2017 12:08 PM
Just tried that, it give me the same error in the agent logs
06/07/17 14:06:40 (983) StartupSequencer SEVERE *** ERROR *** test failure
java.lang.IllegalStateException: User cannot be authenticated or is 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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-08-2017 09:00 AM
I just had a similar issue in my lab. I tried reinstalling and changing directories but that didnt really work. In the end I changed the password of the MID server user in the ServiceNow instance and I cleaned out registry files using CCleaner. Unfortunately I did both at the same time so cant confirm which of the two solved my issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2021 04:32 AM
on my PDI, I did not create a mid server user name's password and setting the password and testing the connection worked out fine for me