Symantec UMC Credential Service will not start or remain started
search cancel

Symantec UMC Credential Service will not start or remain started

book

Article ID: 229817

calendar_today

Updated On:

Products

Data Center Security Server Advanced

Issue/Introduction

Both "Symantec UMC Credential Service" and "Symantec UMC Telemetry Service" will not start and, or remain started. It had previously worked with no known changes to the account or password.

The log file "C:\Program Files (x86)\Symantec\Data Center Security Server\Server\umc\logs\symc-credsync.log" contained an entry similar to the following error:

Caused by: java.sql.SQLException: Login failed for user 'umcadmin'.
 at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
 at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2893)
 at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2335)
 at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:609)
 at net.sourceforge.jtds.jdbc.JtdsConnection.<init>(JtdsConnection.java:369)
 at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:183)
 at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
 at java.sql/java.sql.DriverManager.getConnection(Unknown Source)
 at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:153)
 at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:144)
 at org.springframework.jdbc.datasource.AbstractDriverBasedDataSource.getConnectionFromDriver(AbstractDriverBasedDataSource.java:196)
 at org.springframework.jdbc.datasource.AbstractDriverBasedDataSource.getConnection(AbstractDriverBasedDataSource.java:159)
 at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
 at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
 ... 72 more
2021-12-06 16:36:43 ERROR CredentialSyncDaemon:264 - CredentialSyncDaemon Thread error: Error creating bean with name 'credentialDaemonService': Unsatisfied dependency expressed through field 'credentialSyncService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'credentialSyncService': Unsatisfied dependency expressed through field 'credentialManager'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'credentialManager': Unsatisfied dependency expressed through field 'cmcNotification'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cmcNotification': Invocation of init method failed; nested exception is java.lang.ExceptionInInitializerError
2021-12-06 16:36:43 INFO  CredentialSyncDaemon:267 - Out of run
2021-12-06 16:36:43 INFO  CredentialSyncDaemon:390 - In shutdown hook method################

 

Environment

Release : 6.9.x

 

Cause

Cause 1: The SQL database could not be found, the service for the SQL instance it was running in was off, or the database was missing or could not be located as specified in the Server.xml file.

Cause 2: During the initial DCS installation, the option to enforce password complexity policy was, by default, turned off and the original password specified didn't meet the normal requirements; but an admin or GPO turned it (Enforce password policy" box) back on.

Explanation: In SQL Management Studio under "Security > Logins" the properties for user umcadmin showed that the box "Enforce password policy" was enabled. But it was not originally enabled by default during the initial installation.

The person installing DCS originally used a simpler password complexity than the normal policy would have allowed. After the installation was complete something or someone enabled the checkbox next to the policy. As a result the password specified during installation didn't work because it didn't meet the complexity of the policy.

Resolution

1: If SQL is stopped, please Start SQL

2: If the DCS and UMCDB are missing, or have been deleted, please restore the database from a backup if it exists. 

3: If this is an issue with password policy enforcement, unchecking the box next to the box "Enforce password policy"  under "Security > Logins" will allow the services to start and remain started.

NOTE: It is possible to reset the password for the umcadmin in SQL Management Studio, but in order to generate the encrypted form of the password to embed in Server.xml it will require a encryption generation utility available only by contacting DCS technical support.