Errors on a new SCOM 2007 R2 Environment
Hi,I installed SCOM on a new environment, with the following servers:* SCOMSERVER01 - Web Console, Console, RMS* SCOMSERVER02 - DB, DW, SQL 2005, Reporting Services* SCOMSERVER03 - MOSS 2007 SP1, SLD 2.0On SCOMSERVER01, I'm having the following events:---------------------------------------Event Type: ErrorEvent Source: Health Service ModulesEvent Category: Data Warehouse Event ID: 31552Date: 26/01/2010Time: 15:58:13User: N/AComputer: SCOMSERVER01Description: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: {064A06D9-0A48-51AC-55A3-5A6EF6ADF80B} Management group: AddIT For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.------------------------------------------------------------------------------Event Type: ErrorEvent Source: Health Service ModulesEvent Category: Data Warehouse Event ID: 31552Date: 26/01/2010Time: 15:56:13User: N/AComputer: SCOMSERVER01Description:Failed to store data in the Data Warehouse.Exception 'SqlException': Sql execution failed. Error 468, Level 16, State 9, Procedure TenantMappingProcessStaging, Line 365, Message: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.Sql execution failed. Error 777971002, Level 16, State 1, Procedure StandardDatasetAggregate, Line 424, Message: Sql execution failed. Error 468, Level 16, State 9, Procedure TenantMappingAggregate, Line 262, Message: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the charindex operation. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance Instance name: Microsoft.Exchange.2010.Reports.Dataset.TenantMapping Instance ID: {6879F237-DB6C-4E18-F210-BF5C13706FF9} Management group: AddIT For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.---------------------------------------Can anyone help me?Sorry for my english.Andre
January 26th, 2010 9:14pm

Hi Andre,Did u see this?http://support.microsoft.com/kb/958979Have you tried installing the newest update?http://blogs.technet.com/kevinholman/archive/2010/01/17/opsmgr-2007-r2-cu1-rollup-hotfix-ships-and-my-experience-installing-it.aspxCheers,John Bradshaw
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2010 1:11am

Hi John,I've insalled that update, and it didn't resolve.I'll try to reinstall my entire environmen.Andre
January 27th, 2010 1:24pm

Hi John,I reinstalled the SCOM and SQL using that collation option, and it worked.Thanks!Andre
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2010 10:36pm

Sorry for digging this up. I have exactly the same error messages and both my OperationsManager databases (the OpsMgr and DW) were installed with collation SQL_Latin1_General_CP1_CI_AS from the start although the SQL server is isntalled with the wrong Collation. I can't reinstall the SQL server alltogether since I have tens of custom reports runnning, therefore I need you opinion as to what issues can I have in the future if I leave everything like it is. Any ideas?
September 16th, 2010 5:24pm

We have the same problem after installation CU3 for SCOM 2007 R2.
Free Windows Admin Tool Kit Click here and download it now
January 18th, 2011 5:53pm

We have the same problem. This must be a bug in CU3 and I haven't heard that CU4 resolved this. If this is true, MS screwed this very much, as before CU3 everything went well and no errors occured!R.E.M. - YEAH!
March 12th, 2011 7:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics