Mid server installation error - Unable to connect to instance

sreedharkaliset
Mega Expert

‎12-29-2019 11:45 PM

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.

Labels:
Preview file
4 KB
0 Helpfuls
  • 4,530 Views
8 REPLIES 8

Monali Patil
Kilo Guru
In response to sreedharkaliset

‎12-30-2019 01:44 AM

Hi sreedharkalisetty,

Delete your mid server file also disable servicenow_midserver from your machine service Once again configure mid server by following this steps.If still there is problem please update me.Also ensure you have outbound access on port 443 to the server running the MID server. This can be done quite easily with a browser.

 

  1. Log in to the Windows host machine where you want to install the MID Server.
  2. Create a folder for the MID Server on the top level of the drive such as ServiceNow\MID Server1.
  3. Download the MID archive file into the new folder.
  4. Right-click the archive and select Extract All.
  5. Navigate to the \agent folder that was created when the file was extracted.
  6. Change directories to the service-now\mid server name\agent folder, and enter the following command to start the MID Server installer: installer.bat.To configure the MID Server manually, skip to Step 12.The MID Server installerThe system opens the MID Server installer.
  7. Use the installer to enter the following information.
    • URL to your instance
    • User credentials to run the MID Server
    • Proxy server connection details
    • MID server name
    • MID server service name

    Note: The MID Server user must have the mid_server role.

  8. From the installer, click Start MID Server
  9. Click Mid Servers List Page.The installer opens the MID Server list from your instance.
  10. Select the MID Server name from the list.

    Note: It may take a few seconds for the MID Server time to establish a connection with your instance.


    The system displays the MID Server record.
  11. From Related Links, click Validate.The MID Server Validated changes to Yes.
  12. To configure the MID Server manually, edit the config.xml file with a text editor such as WordPad:
    1. Find the element <parameter name="url" value="https://YOUR_INSTANCE.service-now.com" /> element and change the value to the URL of your instance.
    2. Enter the MID user credentials in the mid.instance.username and mid.instance.password parameters.By default, the MID Server, uses basic authentication for SOAP messages. The password value is also encrypted authentication.
    3. (Optional) Find the <parameter name="name" value="YOUR_MIDSERVER_NAME_GOES_HERE" /> element and change the value for the MID Server name.
    4. (Optional) Enter connection information for the proxy server. Remove the appropriate comment tags from the proxy configuration information.For example, you can configure these parameters:
      • mid.proxy.use_proxy
      • mid.proxy.host
      • mid.proxy.port
      • mid.proxy.username
      • mid.proxy.password
  13. If you configured the MID Server manually, finalize the configuration as follows:
    1. Execute the batch file start.bat.The system starts the new MID Server.
    2. Log into the instance.
    3. Navigate to MID Servers > Servers.The system displays a list of MID Server records.
    4. Select the record matching your new MID Server and verify that the Status is listed as Up.

 

 

If my answer is helpful please mark as Correct/helpful

 

Regards,

Monali Patil

Developer

Preview file
119 KB
Preview file
45 KB
0 Helpfuls

Inactive_Us2002
Kilo Guru

‎12-30-2019 01:05 AM

Hi sreedharkalisetty,

1. If you are working on local system you need install MID Server on the same machine in which you are opening Instance.

2. Make sure user name and password is properly entered in mid server config file and also that user should have mid server role in service now.

If my answer helped you Mark as Helpful/Correct.

0 Helpfuls

khadija3
Tera Guru

‎12-30-2019 01:12 AM

Hello,

Access to the servicenow instance does not always mean the mid server can access, you can try telnet the instance using the port 443 to check the connection

0 Helpfuls

Niraj Kumar
Kilo Explorer

‎09-02-2021 02:46 AM

Hi Team,

I have done proxy setup for mid server access. Its a reverse proxy. I am passing my instance URL to the proxy machine. SSL is configured and able to ping the instance. The intent of doing this is to allow the host machine (where mid server is installed) to access the internet via proxy for servicenow. I am getting the following, any one have idea how to fix this error.

 

MIDServer DEBUG: Event: RGRPerfMetricEvent
MIDServer WARNING *** WARNING *** MIDRemoteGlideRecord.query failed, retrying in 113 seconds
MIDServer WARNING *** WARNING *** Method failed: (https://<xxxx>.service-now.com/file_discovery_agent_sync.do?SOAP&displayvalue=all&redirectSupported=... 400 Bad Request with code: 400
MIDServer SEVERE *** ERROR *** getRecords failed (Method failed: (https://<xxxxx>.service-now.com/file_discovery_agent_sync.do?SOAP&displayvalue=all&redirectSupported... 400 Bad Request with code: 400)
MIDServer DEBUG: Event: RGRPerfMetricEvent
MIDServer WARNING *** WARNING *** MIDRemoteGlideRecord.query failed, retrying in 120 seconds

Kindly suggest the resolution. Thanks


 

0 Helpfuls