none
SQL 6.6.3.0 MP breaks SCOM datawarehousing? RRS feed

  • Question

  • SCOM Datawarehouse is failing with SQL 6.6.3.0 as released on 11/12/2015

    'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '4173391e-ce71-1369-c358-17030bb09b41', Management Pack Version-dependent Id: 'a2bce88f-fcf8-ddcb-7b0f-4d343e766e78'; Target: Database, Server name: 'XXXXXXX', Database name: 'OperationsManagerDW'. Batch ordinal: 42; Exception: Operand data type uniqueidentifier is invalid for max operator.

    Backend is SQL 2008R2 (10.50.6220.0). SCOM is 2012 SP1 Update Rollup 10 (7.0.9538.1136)




    • Edited by andreww Friday, November 13, 2015 12:30 PM
    Friday, November 13, 2015 12:16 PM

Answers

All replies

  • Great... :-( Thanks Andrew.

    Anyone else experiencing that? If so, please vote up on the origin posting.

    Cheers,
    Patrick


    Please remember to click 'Mark as Answer' on the post that helped you.

    Patrick Seidl (System Center and Private Cloud)
    s2 - seidl solutions
    Blog: http://www.systemcenterrocks.com

    Friday, November 13, 2015 12:25 PM
  • That is unrelated to the previous issue that should be solved?

    http://thoughtsonopsmgr.blogspot.nl/2015/11/updated-mp-sql-server-6630.html

    I haven't seen any others having this issue but i'm not that eager to try it out...

    Monday, November 16, 2015 2:50 PM
  • We're a very new installation here, so would never have ran into the 6.6.2.0 error.

    Is there any way I can get more logging about what's going on here, to see if we can shed any light (presuming the OpsMgr team don't read these forums... if I'd released a new MP I'd be keeping an eye on the forums for any issues, personally...)

    Alert: Data Warehouse failed to deploy database component

    Source: 4eb45a81-3c7e-4df6-aab7-5a7ef2669d82

    Path: Not Present

    Last modified by: System

    Last modified time: 11/16/2015 2:48:44 PM Alert description: Data Warehouse failed to deploy database component. Failed to deploy Data Warehouse component. The operation will be retried.

    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '4173391e-ce71-1369-c358-17030bb09b41', Management Pack Version-dependent Id: 'a2bce88f-fcf8-ddcb-7b0f-4d343e766e78'; Target: Database, Server name: 'XXXXXX', Database name: 'OperationsManagerDW'. Batch ordinal: 42; Exception: Operand data type uniqueidentifier is invalid for max operator.

    One or more workflows were affected by this.

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component

    Instance name: 4eb45a81-3c7e-4df6-aab7-5a7ef2669d82

    Instance ID: {2D7BCA04-3564-6CB3-6A58-8523DDEE4663}

    Management group: XXXX


    Monday, November 16, 2015 2:54 PM
  • I'm getting the same issue but only on one of my management servers.

    Failed to deploy Data Warehouse component. The operation will be retried.
    Exception 'DeploymentException': Failed to perform Data Warehouse component deployment operation: Install; Component: Script, Id: '4173391e-ce71-1369-c358-17030bb09b41', Management Pack Version-dependent Id: 'a2bce88f-fcf8-ddcb-7b0f-4d343e766e78'; Target: Database, Server name: 'XXXX', Database name: 'OperationsManagerDW'. Batch ordinal: 42; Exception: Operand data type uniqueidentifier is invalid for max operator. 

    One or more workflows were affected by this.  

    Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component 
    Instance name: cac1b4cd-bbce-44fa-877a-f81cf1a8e122 
    Instance ID: {2BC56C95-F902-5537-2612-9035933784DE} 
    Management group: XXXX


    Monday, November 16, 2015 7:56 PM
  • Same Issue here, got no clue where to look

    Data Warehouse failed to deploy database component. Failed to deploy Data
    Warehouse component. The operation will be retried.
    Exception
    'DeploymentException': Failed to perform Data Warehouse component deployment
    operation: Install; Component: Script, Id:
    '4173391e-ce71-1369-c358-17030bb09b41', Management Pack Version-dependent Id:
    'a2bce88f-fcf8-ddcb-7b0f-4d343e766e78'; Target: Database, Server name:
    'XXXXX', Database name: 'OperationsManagerDW'. Batch ordinal: 42;
    Exception: Operand data type uniqueidentifier is invalid for max operator.

    Tuesday, November 17, 2015 2:09 PM
  • That's the downside with it - no point of contact for escalation (that I've seen, as yet), and no way to debug them?

    Can you upvote the topic at least and hopefully someone will take notice?

    Tuesday, November 17, 2015 2:23 PM
  • I've upvoted and also posted the issue on the SQL Release blog:

    http://blogs.msdn.com/b/sqlreleaseservices/archive/2015/11/12/released-system-center-management-pack-for-sql-server-and-replication-6-6-3-0.aspx

    I've created feedback in connect for this issue. Please upvote it:

    Connect


    Tuesday, November 17, 2015 2:56 PM
  • The new version 6.6.4.0 with fixes for above issues is available:

    • Fixed an installation issue on SQL Server 2008
    • Fixed permission grants for Alert aggregation table

    SQL MP

    SQL MP 2014

    

    Wednesday, November 18, 2015 10:18 PM
  • Who's going to eat that (green?) banana? :-)

    Please remember to click 'Mark as Answer' on the post that helped you.

    Patrick Seidl (System Center and Private Cloud)
    s2 - seidl solutions
    Blog: http://www.systemcenterrocks.com

    Thursday, November 19, 2015 7:02 AM
  • Hi...when going to the link: https://www.microsoft.com/en-us/download/details.aspx?id=10631 to download it seems like the SQLServerMP is still version 6.3.3.0 although the doc's are the updated 6.3.4.0 ones....am I missing something?....should the installation package not install to folder 6.3.4.0 ?

    Timestamp of file is also 9 Nov 2015 which is same as version 6.3.3.0

    Can someone please confirm...


    • Edited by Tommy_tech Thursday, November 19, 2015 7:56 AM
    Thursday, November 19, 2015 7:41 AM
  • Yep, extracts to 6.6.3.0 folder.. :(

    A quick unzipping of some of them still shows 6.6.3.0 in version.txt, and as you see, 9/Nov/15.

    Thursday, November 19, 2015 10:04 AM
  • the right version 6.6.4.0 now on download site
    • Marked as answer by andreww Monday, December 14, 2015 9:43 AM
    Thursday, November 19, 2015 2:56 PM
  • seems like version 6.6.4.0 sorted my issues for me "touch wood". Dashboards are all displaying and no errors
    • Edited by Tommy_tech Thursday, November 19, 2015 3:21 PM
    • Marked as answer by andreww Monday, December 14, 2015 9:43 AM
    • Unmarked as answer by andreww Monday, December 14, 2015 9:43 AM
    Thursday, November 19, 2015 3:20 PM
  • That's odd.... I pulled the latest from http://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx (and also tried direct from SCOM) and I'm still seeing 6.6.3.0 as the latest...? (Page says 6.6.4.0, but it's still downloading 6.6.3.0...)

    PS C:\SCOM MPs\SQL 6.6.4> get-filehash sqlservermp.msi

    Algorithm       Hash
    ---------       ----
    SHA256          28280E6A6EC33E12C46F7C7AE5ED16472887FBFE8C4C3EDF95BE54441DFAB4DA


    • Edited by andreww Thursday, November 19, 2015 4:17 PM
    Thursday, November 19, 2015 4:16 PM
  • That's odd.... I pulled the latest from http://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx (and also tried direct from SCOM) and I'm still seeing 6.6.3.0 as the latest...? (Page says 6.6.4.0, but it's still downloading 6.6.3.0...)

    PS C:\SCOM MPs\SQL 6.6.4> get-filehash sqlservermp.msi

    Algorithm       Hash
    ---------       ----
    SHA256          28280E6A6EC33E12C46F7C7AE5ED16472887FBFE8C4C3EDF95BE54441DFAB4DA


    Usually it takes few days or so while Download page and wki are synchronized. If you want it faster use the download page
    Thursday, November 19, 2015 4:38 PM
  • 6.6.4.0 is not too bad, we upgraded from 6.6.0.0.

    We found that at first views were all over the place, this took approx. 48 hours to settle down (we have a larger estate of 1000+ Databases with a few hundred instances). What we did find was that we were still seeing "client disconnected" when attempting to view any of the new dashboards. We downed the DW and moved it off of an aging Dell PowerEdge R815 onto New Dell PowerEdge R920 (DW is virtualised). Once we did this everything started working. Looks like the aggregations need a *LOT* of raw CPU power. the DW wasn't busy before (5-10% CPU) the 920's are MUCH quicker boxes in terms clock speed and core counts.


    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer". I do not work for Microsoft, I manage a large estate in the public sector, my views are generally first hand production experiences.

    Wednesday, November 25, 2015 11:37 AM
  • Hi Sir,

    How are things going ?

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    Monday, December 14, 2015 8:28 AM
    Moderator
  • The link on the MP download site was fixed, so the right pack has resolved this now. Case closed :D
    Monday, December 14, 2015 9:43 AM