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.
Public
Sysadmin
DBCreator
DBOwner
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 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 ...Startup issue in Linux after fresh installation_Error code 10001
In certain scenario, the application cannot be started just after the fresh install. Below are the error traces, [06:24:57:427]|[10-11-2021]|[pglog]|[INFO]|[18]: -sh: 1: /root/ManageEngine/ServiceDeskPlus-MSP/pgsql/bin/pg_ctl: Permission denied| ...Unable to start the application after power failure
Issue: In certain cases, after a power failure, when the server restarts, the application fails to start and we could see indexoutofboundsexception in the log traces. Cause: This error occurs because the license file gets corrupted which may be due ...Application Startup Issue : Failed to format system error message (Error: 1813)
Issue : Able to start the application from Command Prompt and not from Services.msc. Worked fine with PGSQL but issue occurs after changing to MSSQL database Error Trace in Wrapper file :-1: Failed to format system error message (Error: 1813) ...