Service Mapping Error identify
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2023 06:09 AM
I am getting the below error while performing discovery for mapping:
Failed to identify CI due to the host 10.***.**.*** lacking an application running on port 1433. Make sure that the application is running and run quick discovery on the host.
- Labels:
-
Orchestration (ITOM)
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2023 06:23 AM
Hi @japlandim
Could you please let me know if you've tried running quick discovery?
Also, there needs to be more detailed info on what you are trying to accomplish. Can you elaborate and share screenshots?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-23-2023 06:57 AM
This error means this particular host is not listening on port 1433.
Verfication Step: if you open this CI in cmdb_ci table, go to TCP connection tab and apply filter 1. IP is host ip 2. type is Listening on. you can see the port 1433 is missing.
Kindly try running quick discovery for this IP.
Mark my ANSWER as CORRECT n HELPFUL if it helped.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2023 02:02 AM
Hi @japlandim,
The error message means that the discovery process couldn't find a CI on the host 10.*..*** because there's no application running on port 1433. Port 1433 is the default port for Microsoft SQL Server, so make sure that the SQL Server application is running on the host. You can also try running a quick discovery on the host.
Here are the steps to troubleshoot the error:
- Check if the SQL Server application is running on the host.
- Run a quick discovery on the host.
If the CI is still not identified, contact your IT administrator for assistance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 02:14 AM - edited 06-27-2023 02:41 AM
The application on port 1433 is not running. Check if it's installed and configured correctly. If it is, restart the app. If not, run a quick discovery on the host. MaryKayInTouch