Unable to start the database

Failed to start the database

For the error "Failed to start the database",
  • Check what database being used and, execute changeDBServer.bat.
  • For Pgsql, 
    • Start PGSQL from the command link, execute StartDB.bat 65432 under C:\Manageengine\ServiceDesk\bin
65432 is the default port used by the bundled Postgres.

    • See if there are any errors. For the complete error list go to, C:\Manageengine\ServiceDesk\pgsql\data\pg_log. Open the file created for the specific day and perform troubleshooting accordingly. 
ServiceDesk Plus will attempt to start the database if Pgsql / Mysql is used. If the database is standalone, stop it from starting by updating the StartDB parameter to false in nms-service.xml found under C:\Manageengine\ServiceDesk\server\default\conf.

  • For MSSQL, if you encounter the following error, 
    • Check whether the database server is reachable from the application server. Check through ping / telnet
    • If it is unreachable, check whether the server that hosts the SQL server is up and running. 
    • If running, check whether the user credentials configured to connect the database has sufficient privileges. 
Common privileges required for the ServiceDesk Plus DB.


Sample traces from Serverout0.txt for the issue logging into the database. 

The issues mostly reported will be due to low disk space in the SQL server. By shrinking the transaction logs / deleting the transaction logs, you can increase the free space. 

                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • Port Occupied / Application Layer Starting

                        If the port is already occupied (as in the screenshot), prompt as in below screenshot will appear.  Find application that uses the port by following the steps below, Execute, netstat -oan (This command will display list of processes and the ports ...
                      • Unable to start the server. On an error / any of the containers(modules) are failed

                        Open the serverout0.txt found under [SDP-Home]\server\default\log using any text editor.  Search for the word 'Exception'. See if there are any known error pertaining to the environment. The most reported are due to 'Low disk space' in the drive. For ...
                      • Unable to connect to the application

                        Checklist :   Check whether the web interface is accessible from the server? Is the URL accessible? Check if there are any errors? Can you connect to the application using the server's IP address? Are there any errors when you start the application ...
                      • How to change the database from MySQL/PostgreSQL to MSSQL

                        The steps mentioned below are applicable only if you migrate the DB from PgSQL to MSSQL. This means that the application server is going to remain the same. The data alone is going to be transferred to MSSQL DB from the existing PgSQL DB.    For ...
                      • Postgres Database startup failures with InitPgsql error trace

                        [com.adventnet.db.adapter.postgres.DefaultPostgresDBInitializer] [SEVERE] : Please login to the system as <machine_name>\Administrator and execute initPgsql.bat script with administrator privileges. If issue is not yet solved, please contact support ...