How can I execute a MsSQLDebug.bat / MsSQLDebug.sh file?
This file is used to check if the connectivity and the Discovery of the MsSQL Server is possible from the Applications Manager installed server. This standalone program is a excerpt of the same process we use to add the MsSQL Server monitor. The usage to run this file is as below
Via command prompt goto AppManager/bin/troubleshooting directory and execute the MsSQLdebug file with the usage below.
Usage : MsSQLDebug.bat [HostName / Ip] [Port Number] [Authentication] [Username] [Password] [SSL Encryption] [Instance Name]
Via command prompt goto AppManager/bin/troubleshooting directory and execute the MsSQLdebug file with the usage below.
Usage : MsSQLDebug.bat [HostName / Ip] [Port Number] [Authentication] [Username] [Password] [SSL Encryption] [Instance Name]
[HostName / Ip] HostName or Ipaddress of machine where MsSQL server is running
[Port Number] Port number of the MsSQL server
[Authentication] SQL (or) Windows based authentication for connecting to MsSQL
[Username] User name for connecting to MsSQL ( For windows authentication , Username should be mentioned as DomainName\UserName )
[Password] Password for connecting to MsSQL
[Instance Name] If you want to connect to the MsSQL using a Named SQL instance, mention the Instance Name otherwise leave it as blank
This will initiate the process to discover the MsSQL Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this you will be able to find If discovery is possible, If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the MsSQL installed server.
For more info or assistance do send us the output of the above command for analysis along with Support Information File.
[HostName / Ip] HostName or Ipaddress of machine where MsSQL server is running
[Port Number] Port number of the MsSQL server
[Authentication] SQL (or) Windows based authentication for connecting to MsSQL
[Username] User name for connecting to MsSQL ( For windows authentication , Username should be mentioned as DomainName\UserName )
[Password] Password for connecting to MsSQL
[Instance Name] If you want to connect to the MsSQL using a Named SQL instance, mention the Instance Name otherwise leave it as blank
[SSL Encryption] SSL Encyption is true if the SQL Server configured for secured connection via SSL protocol. It will be false for Non-SSL/TLS connections.
For Kerberos authentication
Usage : MsSQLDebug.bat [Database_FullyQualified_HostName] [Port Number] [Authentication] [Password] [Instance Name]
[Database_FullyQualified_HostName] HostName where MsSQL server is running. Fully Qualified Domain Name should be specified If Kerberos authentication is chosen. For example : mssql-test-1.mykerberos.com where mssql-test-1 is SQL server's host and mykerberos.com is its domain name.
[Port Number] Port number of the MsSQL server
[Authentication] Should be specified as 'Kerberos'. Kerberos based authentication for connecting to MsSQL
[Password] Kerberos Principal password for connecting to MsSQL ( If ticketCache or Keytab is configured for connection then give password as null, otherwise enter the password )
[Instance Name] This is optional. If you want to connect to the MsSQL using a Named SQL instance, mention the Instance Name otherwise leave it as blank
Note: If you run using Named SQL instance, then you can enter a dummy port number in the monitor and debug script as well.
Note: If you run using Named SQL instance, then you can enter a dummy port number in the monitor and debug script as well.
This will initiate the process to discover the MsSQL Server and on success will also fetch the data for the default attributes monitored and shown as the output. From this you will be able to find If discovery is possible, If data is returned for all attributes or not. In case there is any issue for an attribute data it'll be shown as null. This infers that the data is not available in that server and has to be checked on the MsSQL installed server.
For more info or assistance do send us the output of the above command for analysis along with Support Information File.
New to ADSelfService Plus?
Related Articles
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 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 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 ...