Previous Topic: Can I Rename CA Data Protection Computers?Next Topic: Clients and Gateways Cannot Connect to CMS


Cannot Connect to CMS Because Database Password Has Changed

Symptom:

I cannot connect to the CMS because the password for the SQL Server database account has changed. When I attempt to connect to a CMS in the Administration Console, I cannot do so. An error message indicates that 'The logon failed' and the error description reads 'Unable to connect to the database. (Startup Error).'

Reason:

CA Data Protection uses a SQL Server database account to access the CMS database. If your administrators have changed the password for this SQL Server account (typically for security reasons), you must supply CA Data Protection with the new password before you restart the CA Data Protection infrastructure.

Solution:

If you restart the infrastructure before supplying CA Data Protection with the new password, you cannot connect to the CMS. The workaround is to run the following command from the \System subfolder of your CA Data Protection installation folder. This command updates CA Data Protection with the new password:

wgninfra -exec wigan/schema/Schema UpdateDBPassword "<DBpassword>"

Where <DBpassword> is the new password for the SQL Server database account that CA Data Protection uses to access the CMS database. If the password includes spaces, remember to enclose it in quotes.

To supply CA Data Protection with a new database password

  1. Log on to the Administration console as an administrator.
  2. Click Tools, Set Database Primary User Password.
  3. Enter and confirm the new password.