No DB bundled with the application error in the logs while starting from windows services

No DB bundled with the application error in the logs while starting from windows services

When not able to start the application from the windows services and it runs in the CMD fine without any issues.

After checking the logs you will find the error trace as "NO DB BUNDLED WITH THE APPLICATION".

If the database is MSSQL please follow the below steps,

Go to /ManageEngine/ME/SupportCenter/server/default/conf --> Edit the file "nms-service.xml" and look for parameter ""StartDBServer".

If it set to "TRUE" change it to "FALSE".

Attached screenshot for better understanding,

          • Related Articles

          • Database migration from MySQL to Postgres/MSSQL in SCP 8.1

            We no longer support the use of MYSQL as database in SupportCenter Plus. Hence, we request our users to migrate to Postgres (which is in-built) or Microsoft SQL. Please follow the below steps to carry out the database migration: 1. Shutdown the ...

          • How to increase the log file count in Version 11.0?

            1.Go to ManageEngine\SupportCenterPlus\conf.  2.Edit the logging.properties file and add the file count to be 30 or 40 (depending on how many files you want) in the location where the pattern = ../logs/serverout%g.txt. 3.Save the file and restart the ...

          • Linux to windows migration

            Please follow the steps to migrate the application from Linux to Windows 1. Stop the application. 2. Take a full backup by referring the below link,  ...

          • How to take console log ?

            This article is common for Servicedesk plus MSP and Supportcenter plus applications. To troubleshoot certain UI issues , JS errors , we need console log (output) from the browser. Steps to follow : 1. Login to the application. 2. Right click on the ...

          • How to Change default password on PGSQL database

            Please do follow the below steps which would assist you in changing the default Postgres password.  1. Stop the application services.   2. Please take a trimmed backup <OR> take a Snapshot of  the Server 3. Open Command Prompt with Admin Privileges ...