After a successful ppm installation, database integration and with db service activated, the startup fails with database deploy error.

Document ID : KB000006809
Last Modified Date : 14/02/2018
Show Technical Document Details

After the CA PPM installation, remote database integration and with db service deployed, the CA PPM startup fails.

The installation was successful but the CA PPM fails to start due to a database deploy error; however the remote database is seen correctly as "available" in NSA.



Errors in the logs (example for MSSQL Server):

ERROR niku.union (none:none:none:none) Clarity15.2.0.213 failed to initialize. 
com.niku.union.config.ConfigurationException: The application failed to start because of a database configuration problem. Please review the application log for specific error information. 

<clarity_home>\.setup\scripts\deploy.xml:108: Could not discover local SQL Server service. Please ensure MS SQL Server is installed correctly on this machine. 



The database (db) service should not be deployed, as we don't want to manage Database services via PPM.. 

This is a specific service to start the database, inherited from older CA PPM versions, and not in use anymore.

Databases are to be started with their own tools and not using CA PPM services.

This db service option will be removed from CSA in the upcoming CA PPM version.



When deployed by error, you'll see the db service with the "service status all" command from the command line; this will have to be removed to achieve a correct database connection.

To remove the db service, execute this command from the command line: "service remove db".

Afterwards CA PPM will not give the database configuration error anymore on starting up.