Solution:
Complete the below troubleshooting steps:
1. On the Microsoft SQL server host go to Start → All Programs → Microsoft SQL server → Configuration Tools → SQL Server Configuration Manager → SQL Server services.
2. Make sure that below services are in 'Running' state:
- SQL Server
- MSSQL$<InstanceName> (Required when using a SQL server instance name)
- SQL Server Browser (Required when using a SQL server instance name)
3. In SQL Server Configuration Manager → SQL Server Network configuration → Protocols for MSSQLServer or SQLEXPRESS (or appropriate name of your SQL Server instance)
- Make sure that TCP/IP is enabled.
- Verify that the TCP/IP port of corresponding IP Address (s) is enabled & active and it is correct.
4. Configure the firewall (if any is present) to allow network traffic that is related to SQL Server and to the SQL Server Browser service
5. Open command prompt window and check if the appropriate port is listening in the Microsoft SQL server host using following command: netstat -an | find "1433"
Default port for SQL Server: 1433 (TCP)
Default port for SQL Server Browser: 1434 (UDP) (Required when using a SQL server instance name)
Note: If you are not using the default SQL server ports, then change the port number in the command as required instead of "1433".
TCP |
0.0.0.0:1433 |
0.0.0.0:0 |
LISTENING |
TCP |
0.0.0.0:1433 |
[::]:0 |
LISTENING |
UDP |
0.0.0.0:1434 |
*:* |
|
UDP |
[::]:1434 |
*:* |
|
6. Open command prompt in Applications Manager host and verify if you are able to connect to the SQL Server port using the following command: telnet SQL Server Hostname 1433
7. In case you have entered incorrect username or password or domain or instance name during installation, you can modify them using step 3 in following link: https://pitstop.manageengine.com/portal/en/kb/articles/how-do-i-migrate-the-ms-sql-db-used-by-applications-manager-to-another-ms-sql-server
8. You can choose default database collation as "SQL_Latin1_General_CP1_CI_AS" in the MS SQL Server. If you want to use different collation, choose any case insensitive database collation.
9. Send exact version of the MS SQL server and then open command prompt window in Applications Manager host and execute the MsSQLDebug.bat file from <Applications Manager Home>\bin\troubleshooting\ directory and copy the result to appmanager-support@manageengine.com
10. If you are using Windows Authentication for connecting to MS SQL database, then you have set the Authentication Mode of the SQL server from "Windows Authentication Mode (Windows Authentication)" to "Mixed Mode (Windows Authentication and SQL Server Authentication)". Learn more
11. If you are using NTLMv2 as security for the MS SQL database server, then open the database_params.conf file located under <Applications Manager Home>\working\conf\MSSQL\ directory using any text editor and add the following parameter as well in the connection string line: ;useNTLMv2=true
Example: url jdbc:jtds:sqlserver://localhost:1433/AMDB;appName=ApplicationsManager;useNTLMv2=true AppModules TopoDB-MapDB-EventDB-AlertDB-PollDB-PolicyDB-USERSTORAGEDB-ApplnDB
12. Please check if you have administrator privileges in the server where you are installing Applications Manager. Also, on the MS SQL server the database user should have administrator privileges.
Send support information file to appmanager-support@manageengine.com, the steps to create support information file is given in here.
Note: Make sure to take backup of existing settings before any modification on the SQL Server. Refer below links for more help: