Troubleshooting MS SQL Monitor Addition Problems
Please refer to the Prerequisites for MS SQL Database Server before adding a monitor.
1. Ensure that the SQL Server is running and accessible.
Try connecting to the SQL Server instance via SQL Server Management Studio or DBVisualizer using the same credentials. This step helps diagnose connection issues, ensuring both the server is reachable and the authentication details are correct. If you can connect successfully with these tools, it indicates that the SQL Server is up and running correctly.
2. Check if the hostname or IP address is resolving correctly from the Applications Manager machine.
Open Command Prompt and execute the following commands:
- nslookup <hostname_or_ip> - This command returns the domain name or IP address, indicating whether the Domain Name System (DNS) can resolve the hostname to an address and vice versa.
- ping <hostname_or_ip> - This command tests the connectivity between your computer and a specified host or IP address.
3. Check if the port can be accessed via telnet from the Applications Manager machine.
Open Command Prompt and execute the following command:
telnet <hostname_or_ip> <port> - This command is checks network connectivity to a specific port on a host.
If the connection is successful, you'll see a blank screen or a prompt indicating the port is open. If unsuccessful, you'll receive an error message, indicating the port is closed or inaccessible.
4. Check the SQL Server Configuration Manager.
Follow the steps below to ensure that TCP/IP is enabled for the SQL Server:
- In the SQL Server Configuration console, click on SQL Server Network Configuration.
- Click on Protocols for MSSQLSERVER/Protocols for SQLSERVER2016 (based on the required instance).
- Under the Protocol Name column, ensure that the status of the TCP/IP is 'Enabled'.
- If the status is set to 'Disabled', double-click on TCP/IP and switch the status from Disabled to Enabled.
- Restart the SQL Server instance.
5. Review potential network issues.
- If the SQL Server is on a different network, ensure there are no network or VPN issues affecting connectivity.
- Verify if the SQL Server has multiple NICs, with one configured to use DHCP and another with a static IP.
- Confirm whether Applications Manager resolves the hostname to the IP address assigned by DHCP (Dynamic Host Configuration Protocol), which may change with DHCP lease renewal or server reboots. This could lead to encountering the error 'Network error IOException: Could not create socket'.
Still facing issues after performing the above troubleshooting steps?
- Execute the MsSQLDebug.bat file located in <AppManager-Home>\bin\troubleshooting and send the results to the Applications Manager support team.
Share the SIF file along with the test credential results and include a screenshot of any additional error messages encountered during monitoring.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...Troubleshooting MS SQL login failure
Problem: The following error message appears in MS SQL monitor during login: "Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication" Solution: Verify if the password of the SQL account (domain\username) ...Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...