Data Protection - How to recover from a corrupt database.properties file on a client installation?

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

CA Data Protection encrypts the local database credentials used by the Endpoint client in the "database.properties" file.  This file is accessed everytime the infrastructure starts up and a backup is created.  These files are sequenced in pairs to avoid corruption (see below).  

 

database.properties, 

database.properties1, 

database.properties.bak, 

database.properties.bak1 

 

These files are susceptible to corruption from anti-virus software and should be excluded from routine checks.  See the link to the product documentation for more information on anti-virus exceptions.

https://docops.ca.com/ca-data-protection/15-2/en/release-notes/ca-data-protection-release-notes/known-issues/tracking-id-705-19-anti-virus-exceptions

 

Question:

When the error "E0028 Infrastructure failed to start correctly. (Unable to read properties file.)" is reported in the activity logs on a client installation it indicates the "database.properties" file has become corrupt.  How can you  recover from this situation?

 

Environment:
CA Data Protection (DataMinder)
Answer:

Delete all the database.properties files (below) files from the %wgndatadir% directory and then run a repair from Windows Control Panel\Programs.  After the repair the program should become operational and a new set of "database.properties" files will be created.

 

database.properties, 

database.properties1, 

database.properties.bak, 

database.properties.bak1