This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello, I had to restore SCOm to another server, as well as the OperationManager and OperationManagerDW databases. After changing the passwords of the Run As accounts, I still have this error:
Event ID 31552
Failed to store data in the Data Warehouse.
Exception 'SqlException': Cannot resolve collation conflict for not equal to operation.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.Configuration
Instance name: Data Warehouse Synchronization Service
Instance ID: {55531A24-64FA-643B-6027-89A07538C191}
Management group: XXX
What to do? Thank you!
Hi @Sébastien Lagueux ,
What SQL Server collation are you using on the new server where you restored your SCOM database & data warehouse? It sounds like your new server has a different collation or an unsupported collation perhaps.
----------
If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!
Best regards,
Leon
Hi Leon
This is a SCOM 2019 and Collation are Latin1_General_CI_AS. It's the collation as my old SCOM server.
Did you clear the agent cache and the console's cache on all SCOM management servers after the restore?
How and When to Clear the Cache
Also check the status of your management group under the Monitoring pane, also check the Operations Manager event log if there are more warnings/errors.
There must be other problems because I am not able to clear agent cache: Failed to connect to an IPC Port: Access is denied. However I am on the server itself.
And another error under my status of my management group:
The partitioning and grooming processes for the operational database (OperationsManager) on the server scom2016 have either not been run recently or have been failing. At the time this alert was raised, the partitioning and grooming process had not completed for days.
Do you have an idea?
As per error said, the issue may be come from collation different between old SQL server and new SQL server.
Set or Change the SQL Server Collation
https://learn.microsoft.com/en-us/sql/relational-databases/collations/set-or-change-the-server-collation?view=sql-server-ver15
Moreover, make sure that your follow
2) How to move the Reporting data warehouse database
https://learn.microsoft.com/en-us/system-center/scom/manage-move-omdwdb?view=sc-om-2019
Roger