How can I execute a MS SQLDebug.bat / MsSQLDebug.sh file?

How can I execute a MS SQLDebug.bat / MsSQLDebug.sh file?

The MsSQLDebug file is a diagnostic tool used to verify connectivity and discoverability of the MS SQL Server from the Applications Manager server. This standalone utility replicates the internal process used when adding an MS SQL Server monitor.

Steps to Execute:
  1. Open Command Prompt (or Terminal for .sh file).
  2. Navigate to the AppManager/bin/troubleshooting directory.
  3. Run the MsSQLDebug file using the following syntax:
Quote
Usage:
MsSQLDebug.bat [HostName/IP] [Port Number] [Authentication Type] [Username] [Password] [SSL Encryption (true/false)] [Instance Name]

Example: 
MsSQLDebug.bat 127.0.0.1 1433 SQL sa "User123" true SQLSERVER16
Notes
Note: Use MsSQLDebug.sh if you are on a Linux system.

Parameter Details:
  1. [HostName/IP] – Hostname or IP address of the machine where the MS SQL Server is running.
  2. [Port Number] – The port number used by the MS SQL Server (e.g., 1433).
  3. [Authentication] – Type of authentication used to connect to MS SQL. Accepted values: SQL or Windows.
  4. [Username] – Username for connecting to MS SQL. For Windows Authentication, format it as DomainName/UserName.
  5. [Password] – Password for connecting to MS SQL. If the password contains special characters, enclose it it in double quotes ("pwd@123").
  6. [SSL Encryption] – Set to true if the SQL Server uses SSL/TLS for secure connections; otherwise, use false.
  7. [Instance Name] – Specify the Named Instance of SQL Server if applicable. Leave it blank for default instances.

Usage for Kerberos Authentication:
Quote
MsSQLDebug.bat  [Database_FullyQualified_HostName] [Port Number] [Authentication] [Password] [Instance Name]

Parameter Details:
  1. [Database_FullyQualified_HostName] – Fully Qualified Domain Name (FQDN) of the MS SQL Server host. For example: mssql-test-1.mykerberos.com (where mssql-test-1 is the hostname and mykerberos.com is the domain).
  2. [Port Number] – Port number of the MS SQL Server. For Named Instances, a dummy port number can be used.
  3. [Authentication] – Must be specified as Kerberos.
  4. [Password] – Kerberos Principal password. Use null if ticketCache or keytab is configured for authentication.
  5. [Instance Name] (Optional) Named instance of the SQL Server. Leave it blank if not applicable.
Notes
Note: When connecting using a Named SQL Instance, you may enter a dummy port number in both the monitor configuration and the debug script. The actual resolution is handled internally via the SQL Server Browser service.
This process initiates the discovery of the MS SQL Server. Upon successful connection, it retrieves data for the default set of monitored attributes and displays them as output. From this, you can determine whether the discovery was successful and whether data is being returned for all attributes. If any attribute shows a value as null, it indicates that the data is not available on the target server. In such cases, further verification must be performed directly on the MS SQL Server to ensure the data is present and accessible.
Info
For more information or assistance, send us the output of the above command for analysis along with the Support Information File.

                  New to ADSelfService Plus?

                    • Related Articles

                    • How to execute ServerSSHTroubleshoot.bat or sh file ?

                      Solution: Execute the file ServerSSHTroubleshoot.bat or sh from the <AppManager_home>\bin\troubleshooting folder (<AppManager_home>\bin in older versions of Applications Manager). Via command Prompt Execute the ServerSSHTroubleshoot.bat or sh file. ...
                    • How can I execute the GlassFishDebug.bat / GlassFishDebug.sh file?

                      Note: Although the script name mentions GlassFish Server, the script file can be used for troubleshooting any monitor connectivity issues, that comes under JMX mode of monitoring like JMXApplications, Apache Zookeeper, Apache Geronimo etc., This file ...
                    • How to execute runWLSMbean.bat or sh file?

                      Execute the runWLSMbean.bat or sh file from the <AppManager_home>\bin\troubleshooting folder via command prompt or terminal. Eg. ~/Zoho/ManageEngine/ManagedServer/AppManager15/bin/troubleshooting$ ./runWLSMbean.sh It will prompt for the details to ...
                    • How can I execute UpdateHostnameandIP.bat/sh ?

                      Here are the steps to execute UpdateHostnameandIP.bat/sh: 1) Execute <AppManager_Home>\bin\troubleshooting\UpdateHostaneandIP.bat/sh file. For example,  updateHostNameAndIp.bat/sh [Previous HostName/IpAddress] [new HostName/IpAddress] ...
                    • How to execute WebsphereMQDebug.bat / WebsphereMQDebug.sh?

                      This file is used to check if the connectivity and the Discovery of the Websphere MQ Server is possible from the Applications Manager server. This standalone program is an excerpt of the same process we use to add the Websphere MQ Server monitor. The ...