tag:blogger.com,1999:blog-4414432572587218573.post2414496951613300658..comments2023-05-06T15:20:16.638+02:00Comments on Thoughts on Azure, OMS & SCOM: Failed to store data in the Data Warehouse. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.Marnix Wolfhttp://www.blogger.com/profile/09487479325587450184noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-4414432572587218573.post-73950475206136490602012-03-26T14:28:05.108+02:002012-03-26T14:28:05.108+02:00Thank you for an easy step-by-step guide to fix th...Thank you for an easy step-by-step guide to fix the collation issue.<br /><br />Used the guide just now, and here are my comments from that experience, for any future operations:<br /><br />As reporting server was on a dedicated server, we tried the operation without reinstalling reporting. It worked fine. We just made sure to backup and restore the reportserver DB as well.<br /><br />SCOM had problems logging into the databases after the restore. We found the SCOM users in the DB, but they were not present under "SQL server\security\logins". As soon as we tried to create those users and give them DB rights, we got an error that they already existed in the DBs, and they magically popped up under \logins as well. Login worked fine then.<br /><br />We also used this Technet guide on "how to move the OperationsManager DB" ,to "set ENABLE_BROKER", http://technet.microsoft.com/en-us/library/cc540384.aspx.<br /><br />Also, event 33333's from DataAccessLayer were spammed on the OperationsManager event log on SCOM RMS, so we used the following easy guide from Aman Dhally to stop the spam, http://opsmgradmin.blogspot.com/2011/05/scom-event-id-33333-in-scom-from-source.html .<br /><br />Finally, had to start my console with the /clearcache option to get rid of an active alert that had dissapeared during the operation, and thus being lost and scared, not able to move or say goodbye. Kevin Holman has a note on that here, http://blogs.technet.com/b/kevinholman/archive/2007/12/19/tired-of-your-console-throwing-errors-or-manually-clearing-your-console-cache.aspx<br /><br />Thanks again, went smooth!vildaugethttps://www.blogger.com/profile/11355450972330089691noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-65900001820130791282012-02-02T12:55:02.875+01:002012-02-02T12:55:02.875+01:00Just testing out SCOM and SCCM 2012, found the por...Just testing out SCOM and SCCM 2012, found the porblem with SCCM, when i looked at SCOM I found the problem also, this is now fixed, thank you for this post, great, nice one...........<br /><br />Dave.......Dillthedoghttps://www.blogger.com/profile/12168702999565937710noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-27684729261824777622012-01-09T14:31:56.471+01:002012-01-09T14:31:56.471+01:00Hi Marnix,
i have run into this problem myself, i...Hi Marnix,<br /><br />i have run into this problem myself, i did follow these steps and i followed the steps except step 5 removing reporting server. <br /><br />"as i thought that it isn't needed"<br />what i did is the following.<br /><br />after reinstalling SQL i recreated the Services Account logins. and started with the restores.<br /><br />it is a well written article many thanks for all your time and effort putting in to SCOM Community.<br /><br />Cheers<br />FaizelFaizelhttps://www.blogger.com/profile/06022699584165051344noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-70259000824798853092011-06-16T23:10:20.931+02:002011-06-16T23:10:20.931+02:00Hi Marnix,
I just ran into the same issue after i...Hi Marnix,<br /><br />I just ran into the same issue after installing the MP for Exchange 2010 (never had this before with any other MP!).<br /><br />I've been digging a bit and it's related to the Windows Locale of the server when you install SQL on the box. <br />See 'Default Collations in SQL Server Setup' at http://msdn.microsoft.com/en-us/library/ms143508.aspx.<br /><br />Only a Windows Locale of English US will default to SQL_Latin1_General_CP1_CI_AS. Lots of other locales Dutch, English UK, etc all default to Latin1_General_CI_AS for the Server Collation. <br />So in my case the Server Collation is Latin1_General_CI_AS, the Database collation of the OperationsManager and OperationsManagerDW are SQL_Latin1_General_CP1_CI_AS.<br /><br />I think MSFT should be aware that most countries do not install their servers with the English US locale ... and this is not the first time we run into "localization issues" with OpsMgr. <br /><br />Cheers,<br />Sergesrgbrthttps://www.blogger.com/profile/04515336899748824018noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-58842621685625851472011-06-16T23:09:07.581+02:002011-06-16T23:09:07.581+02:00Hi Marnix,
I just ran into the same issue after i...Hi Marnix,<br /><br />I just ran into the same issue after installing the MP for Exchange 2010 (never had this before with any other MP!).<br /><br />I've been digging a bit and it's related to the Windows Locale of the server when you install SQL on the box. <br />See 'Default Collations in SQL Server Setup' at http://msdn.microsoft.com/en-us/library/ms143508.aspx.<br /><br />Only a Windows Locale of English US will default to SQL_Latin1_General_CP1_CI_AS. Lots of other locales Dutch, English UK, etc all default to Latin1_General_CI_AS for the Server Collation. <br />So in my case the Server Collation is Latin1_General_CI_AS, the Database collation of the OperationsManager and OperationsManagerDW are SQL_Latin1_General_CP1_CI_AS.<br /><br />I think MSFT should be aware that most countries do not install their servers with the English US locale ... and this is not the first time we run into "localization issues" with OpsMgr. <br /><br />Cheers,<br />Sergesrgbrthttps://www.blogger.com/profile/04515336899748824018noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-17155690067723943662010-12-03T14:23:00.493+01:002010-12-03T14:23:00.493+01:00Hi Moe.
In the posting I write what to do about t...Hi Moe.<br /><br />In the posting I write what to do about the SQL server. So the Agent only needs to be reinstalled on the SQL server.<br /><br />Would be a bit of a drama when ALL the Agents needed a reinstall.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-79255782359319739852010-05-01T14:13:40.001+02:002010-05-01T14:13:40.001+02:00Hi Kim.
Thanks for visiting my blog. The collatio...Hi Kim.<br /><br />Thanks for visiting my blog. The collation setting also applies to SQL Server 2005. Taken from the mentioned webpage in this article: 'SQL collation must be SQL_Latin1_General_CP1_CI_AS; no other collation configurations are supported<br />'<br /><br />So where it comes down to, is that when you experience any issue and you contact Microsoft PS and they find out the collation to be 'out-of-order', you may enter 'the realm of unsupported configurations'.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-9701641005400121612010-05-01T14:09:25.232+02:002010-05-01T14:09:25.232+02:00Hi Kim,
No. It is not a typo. I really mean CU#7 ...Hi Kim,<br /><br />No. It is not a typo. I really mean CU#7 for SQL Server 2008 SP1: http://thoughtsonopsmgr.blogspot.com/2010/04/cumulative-update-7-for-sql-server-2008.html<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-85040858116662209672010-04-30T18:36:27.814+02:002010-04-30T18:36:27.814+02:00....oh, by the way, in your #9 above, I think you .......oh, by the way, in your #9 above, I think you mean CU# 3, not CU# 7.<br /><br />- KimUnknownhttps://www.blogger.com/profile/02087923510092245064noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-57663395383488665092010-04-30T18:30:34.714+02:002010-04-30T18:30:34.714+02:00Marnix,
Do you think this only applies to SQL 200...Marnix,<br /><br />Do you think this only applies to SQL 2008 (and not 2005)? <br /><br />I am about to upgrade SQL (2005 -> 2008) in a SCOM 2007 R2 installation and found your post. Went back and checked my site and found that the existing SQL 2005 *server* has "Danish_Norwegian_CI_AS" but the *databases* have "SQL_Latin1_General_CP1_CI_AS" as they should. But everything has been running smoothly. Somewhat scared I went back and checked the event logs and found some 31552 events posted during the SCOM SP1 -> R2 upgrade, but they stopped sometime during the process and haven't been seen since (sorry, I can't pinpoint exactly what step in the upgrade caused the events to stop).<br /><br />So now I am worried that once I upgrade SQL to 2008 I will start seeing them again. Any thoughts?<br /><br />- KimUnknownhttps://www.blogger.com/profile/02087923510092245064noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-76323233389116399382010-04-29T15:34:26.461+02:002010-04-29T15:34:26.461+02:00Hmmm that's a death end then ;-)
If I have tim...Hmmm that's a death end then ;-)<br />If I have time the upcomming days maybe I can test this in a test environment. Will let you know...OskarLhttps://www.blogger.com/profile/11365100122742185113noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-63728602845344885162010-04-29T15:25:03.754+02:002010-04-29T15:25:03.754+02:00Hi Oskar.
The PreReq Tool did not gave any clue w...Hi Oskar.<br /><br />The PreReq Tool did not gave any clue what so ever...<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-34189992234108786882010-04-29T15:21:39.789+02:002010-04-29T15:21:39.789+02:00Hi Oskar.
Thanks for your comment. I updated my b...Hi Oskar.<br /><br />Thanks for your comment. I updated my blogposting accordingly.<br /><br />Cheers,<br />MarnixMarnix Wolfhttps://www.blogger.com/profile/09487479325587450184noreply@blogger.comtag:blogger.com,1999:blog-4414432572587218573.post-15007356851090393212010-04-29T15:11:16.335+02:002010-04-29T15:11:16.335+02:00Hi Marnix,
Have run into this one myself. As far ...Hi Marnix,<br /><br />Have run into this one myself. As far as I can recall the prereq gave a warning on the collation settings prior to installation.<br />During my investigation I run into a part from the Quick Start guide which actually mentions this.It is under minimum software requirements.<br />http://technet.microsoft.com/en-us/library/bb309428.aspx<br /><br /><br />Great you finally solved it although it was a long way ;-)<br /><br />Cheers.<br />Oskar LandmanOskarLhttps://www.blogger.com/profile/11365100122742185113noreply@blogger.com