Application Service Mapping

Mvakazi
Tera Contributor

Hi,

I am mapping application services and they fail with error "Failed to identify CI due to the host xxxx lacking an application running on port 1433" as we are not using this port to connect. Can you please advise on what I need to do so the pattern MSSql DB on Windows can recognise the port being used.

 

Looking forward to your assistance.

 

Mvakazi

3 REPLIES 3

User342536
ServiceNow Employee
ServiceNow Employee

Hi @Mvakazi 

 

Try to rediscovery (horizontal discovery) host, and check the port MSSQL is using. Normally, in top-down discovery MSSQL connections comes from IIS Virtual Directorty, that uses ADO .NET connection to get connection strings to MSSQL.

 

Also, check connection suggestions, to get correct port MSSQL is running on, and force downstream connection from the uplevel.

 

Kindest Regards,

 

Rodrigo Donnangelo

Please mark the answer as helpful and correct if helped.

SK Chand Basha
Giga Sage

Hi @Mvakazi 

 

To view processes in Windows CI , check the "Related List"  - TCP Connections to see where the connection(Connects to) is being made check the port number and try it.

 

SKChandBasha_0-1731130290883.png

 

 

If the Windows system is related to an MS SQL database, you will be able to see it listed under the "Related Items" section.

 

Mark it Helpful and Accept Solution !! If this helps you to solve the issue.

Niklas Peterson
Mega Sage
Mega Sage

Hi,
If you are not using the default port of 1433 then you need to create a custom IP Service for the port you are actually using. 

NiklasPeterson_0-1731154580090.png

Regards,
Niklas