Solarwinds Service Graph connector URI error

Nisha30
Kilo Sage

3 weeks ago

Hello Experts,

 

Need your urgent help here what am i missing.

 

We are integrating ServiceNow with Solarwinds using Service Graph connector .

1.   Firewall port TCP on 17774 is allowed

2. Permissions on SWIS API given by Solarwinds team.

3. MidServer is up and running.

 

Still when we try to connect it gives error as below. Is there any extra step . Solarwinds team says they have given permission

 

Not sure how to proceed.

 

Thanks

Preview file
121 KB
0 Helpfuls
  • 889 Views
7 REPLIES 7

Tanushree Maiti
Kilo Patron

3 weeks ago

Hi @Nisha30 

 

Probable cause could be -

1. Double-check the SolarWinds hostname and port specified in the HTTP Connection within ServiceNow . 

 From Host system of the MID Server, use network tools like ping/telnet to confirm connectivity to the SolarWinds hostname and port.

 

2.  Ensure the user account configured for the integration has the correct roles and permissions, and that the password is correct.

 

3. Check the agent logs in the MID Server installation directory for more specific error messages like authentication issue/access issue

 

Refer: 

1. https://www.servicenow.com/community/developer-forum/host-name-is-not-retrieved-by-midserver/m-p/267....

 

 

 

 

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.
Regards
Tanushree Maiti
ServiceNow Technical Architect
Linkedin:

Nisha30
Kilo Sage
In response to Tanushree Maiti

3 weeks ago

Hi @Tanushree Maiti 

 

Yes roles and permissions are given in Solarwinds. But there is this URI error comming.

 

What exact URL has to open from browser from MidServer???

 

Thanks

0 Helpfuls

Vijaya_Mnpram
Kilo Sage
In response to Nisha30

3 weeks ago

@Nisha30  You need to login to the MID server and open the command prompt (by typing cmd in the start command).

After you open the command prompt, you need to just type "telnet <hostname> <portName>"

If the command prompt says, 'telnet' is not a recognized comman, then the telnet is not installed on the MID server. Hosting team can help you.

If the test is successful, then the connection from MID server to Host is working fine. then you can debug the ECC messages to check the connection between MID server and servicenow. 

Nisha30
Kilo Sage
In response to Vijaya_Mnpram

2 weeks ago

Hi @Vijaya_Mnpram  yes the connection is opened however telnet is not allowed due to security (so SME had helped in same.)

However the URI which is in error that URL does not open in browser.

 

What exact URL has to open in browser is that the same which is in error and in connection URI ?

 

Thanks

0 Helpfuls