Event 31552 - Collation issue
Hello there,
I get the following events (and similair) every 10 minutes. The instances are MS Exchange MP related.
----
Failed to store data in the Data Warehouse.
Exception 'SqlException': Sql execution failed. Error 777971002, Level 16, State 1, Procedure StandardDatasetAggregate, Line 424, Message: Sql execution failed. Error 468, Level 16, State 9, Procedure AvailabilityAggregate, Line 535, Message: Cannot resolve
the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
One or more workflows were affected by this.
Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance
Instance name: Microsoft.Exchange.2010.Reports.Dataset.Availability
Instance ID: {9FDEB7D1-AE40-7CFC-CECC-300B8797404C}
Management group: groupxxx
------
Collation setting for both the OpsMgr and DW database are SQL_Latin1_General_CP1_CI_AS.
The collation setting for the SQL instance, Report and ReportTemp database are Latin1_General_CI_AS.
According to this info:
http://technet.microsoft.com/en-us/library/bb309428.aspx all SCOM databases should have SQL_Latin1_General_CP1_CI_AS collation. Does that also apply to the Report and ReportTemp databases? If so, are there any best practices to change the collation
for these databases.
Any help would be great.
Regards,
Chris
May 17th, 2011 9:13am
Hi,
There is only one way to change a server collation - reinstall a SQL Server.http://OpsMgr.ru/
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2011 9:29am
So I guess re-installing SCOM Reporting Server and SQL Reporting services and related databases will do the job? Is that correct? The SQL Server instance setting for collation will be unchanged this way, but I assume that this setting is only a default setting
that the databases you create will get, if you don't set your own preferred collation setting when creating those databases. Right?
Thank you in advance.
May 18th, 2011 2:35pm
Hi,
Regarding your queries, I would like to share the following with you for your reference:
SQL collation "SQL_Latin1_General_CP1_CI_AS" needs to be designated for installing OpsMgr DB
http://support.microsoft.com/kb/958979
Setting and Changing Collations
http://msdn.microsoft.com/en-us/library/ms177439.aspx
Hope this helps.
Thanks.
Nicholas Li - MSFT
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 11:59pm
Hi again,
I've decided to reinstall SQL Reporting Services and SCOM Reporting and set the collation right this time for the Report and ReportTemp databases (as these were the ones having the wrong collation setting). However when installing SQL Reporting Services
there is no way to change the collation. It just takes the default instance collation setting which is Latin1_General_CI_AS.
Is there a way to change the default instance collation setting?
Thanx in advance.
May 23rd, 2011 9:10am
>Is there a way to change the default instance collation setting?
No. You have to reinstall SQL Server instance (SQL DB Engine).http://OpsMgr.ru/
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 9:56am
You cant change the collation. Have to start again with installing SQL and use the right collation at that point. SorryBob Cornelissen - BICTT (My BICTT Blog)
May 23rd, 2011 12:40pm
Ok that's too bad. However I think I could restore the OpsMgr database after reinstalling SQL server, as it has the right collation already. I will then build up the SCOM Reporting again with its databases (OpsMgrDW, ReportDB, ReportTempDB). Does that
sound like a plan or am i missing something here?
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 2:17pm
Yes, it does.http://OpsMgr.ru/
May 24th, 2011 1:04am
Hi,
Regarding restoring database, I would like to suggest you refer to the following guide:
How to Restore Operations Manager 2007 Databases
http://technet.microsoft.com/en-us/library/cc540396.aspx
Hope this helps.
Thanks.Nicholas Li - MSFT
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2011 4:30am
Thanx all!
May 24th, 2011 9:28am
I've restored the OpMgr database and installed SCOM Reporting again. There are a few problems I am having right now. The MS server is greyed out and no alerts are being received. I've changed the primary server to the RMS for a couple of agents, but still
no alerts are being received. For instance when I stop an agent, the state for the agent is going grey, but no alert is generated.
The following event on the RMS is generated every 10 seconds or so:
-----
Event 2115
A Bind Data Source in Management Group SCOMgroup has posted items to the workflow, but has not received a response in 1020 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectPerformanceData
Instance : serverA.domain
Instance Id : {A4D4B1CD-3503-675B-3BC9-D04989E8B621}
-------
Pls advice what to do. Thanx.
Free Windows Admin Tool Kit Click here and download it now
June 6th, 2011 6:53am
The OpsMgr Management Action Account could not logon to the SQL server instance because it did not have any login. This also was the case for the OpsMgr SDKCSA account but I created this one immediately after restore of the database. I forgot to recreate
the Management action account unfortunately.
Furthermore I also had errors like in the following blog:
http://thoughtsonopsmgr.blogspot.com/2010/08/eventid-4502-and-how-to-troubleshoot-it.html The described fix did solve the problem.
Just restoring the OpsMgr database did not give me back all settings, which is very logical, as some required settings were instance related.
June 6th, 2011 9:24am