If the SymantecCCS service fails to start after deleting the log files in step 3, go to C:\windows\ADAM\ and run the DsdbUtil.exe file to perform the integrity check.
At the dsdbutil.exe: prompt, type files and
At the file maintenance: prompt, type Integrity.
Run the Symantec.CSM.ConfigureServiceAccount.exe located at <installation_directory>/CCS/Reporting and Analytics/Application Server/ to set the service accounts and database connections.
On the SQL Server Management Studio, detach the CCS SQL Server databases.
Delete the existing CCS databases and copy the backed up SQL Server databases.
Attach the backed up SQL Server databases in the SQL Server Management Studio.
Activate SQL Broker.
Evaluation synchronization and default global synchronization fails if you do not activate the SQL Broker.
Run the following command on the SQL Server to check the SQL Broker status: select is_broker_enabled from sys.databases where name = 'CSM_Reports'.
Run the following command to activate the SQL Broker: exec spManageUDMSQLBroker 1, 'dbo', 'CSM_Reports', 1.
If you have moved the database to another computer, run the following command to set the authorization to CSM_Reports database: ALTER AUTHORIZATION ON DATABASE::CSM_Reports TO sa ALTER DATABASE CSM_Reports SET ENABLE_BROKER with rollback immediate.
Restart all CCS services.
Launch the CCS Console.
Go to Settings > Secure Configuration and verify the CCS Application Server credentials and database connections.
Verify that migrated asset structure, assets, collections, evaluations and reports are displayed in the CCS Console.
Verify that all user defined jobs are functional.
Imported Document ID: HOWTO76929
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe