Mid server installation error - Unable to connect to instance

[sreedharkaliset]

Hi All,

I am trying to install Mid server on my machine, when I enter the instance name, user name, password and test the connection, installer is showing me an error "Unable to Connect to instance".

Instance and user credentials are valid and user has mid_server role assigned.

Please help.

[Alberto Consonn]

Hi,

did you check if you can reach your ServiceNow instance from your Mid Server machine? Otherwise please follow the instructions below:

Symptoms

During MID server upgrade (any version) especially manual, while configuring instance connectivity setup process with Proxy server enabled and when clicking on "Test your connection" it'll throw an error "Unable to connect to instance".

Release

• All versions

Cause

• During MID server manual upgrade, post providing Proxy details and clicking "Test your connection", an error message pops-up stating "Unable to connect to instance".
• When analyzing the mid_installer.log file, the below error will be logged.

Resolution

• The error states that the Proxy server is enabled with "NTLM Authentication".
• In order to avoid this error and proceed with upgrade/installation, Proxy team has to disable "NTLM Authentication".

Additional Information

• By default, ServiceNow supports only Basic Authentication against the Proxy server. 
• If the installation has to be successful, Customer has to either disable "NTLM Authentication" or create an exception for the MID host.

If I have answered your question, please mark my response as correct and/or helpful.

Thank you very much

Cheers
Alberto

[sreedharkaliset]

Hi Alberto,

I tested and am able to connect to ServiceNow instance from the machine where I am trying to install mid server. Also, I used simple authentication without any proxy as suggested in above article but I am still facing the same issue.

I was able to connect the same machine successfully to a madrid instance earlier which is not working now with a latest NewYork instance.

Regards,

Sreedhar

[Monali Patil]

Hi sreedharkalisetty,

The agent_keystore.jks file is corrupted. This is the file which will encrypt the MID user password on the config.xml file.You can check in that file.

If this is  a problem Do this:

1. From the services panel, stop the MID server service from running
2. Navigate to agent\keystore directory on the MID server installation directory, and delete the agent_keystore.jks file
3. Open config.xml file, remove the encrypted value for the "mid.instance.password" parameter, and re-enter the password in plain text
4. Scroll all the way to the bottom of the file, and remove the value for the parameter "keypairs.mid.id", and leave it as a blank value 
5. Save the file, and restart the MID server service from the services console

If my answer is helpful please mark as Correct/helpful

Regards,

Monali Patil

Developer

[sreedharkaliset]

Hi Monali,

I tried above but it is still not working, Mid server is not yet available in ServiceNow instance.

Regards,

Sreedhar