locked
Data Warehouse Database Component Deployment State Alert RRS feed

  • Question

  • I am getting the following error in my event logs on my root management server:

    Date and Time:

    12/15/2009 11:59:02 AM

    Log Name:

    Operations Manager

    Source:

    Health Service Modules

    Event Number:

    31565

    Level:

    1

    Logging Computer:

    RootManagement

    User:

    N/A

    Description:

    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: 'e27ba6b3-43c5-1617-b1e4-29ece3abf589', Management Pack Version-dependent Id: '1a6256f5-34ab-fbb2-4223-8a6ad73a196c'; Target: Database, Server name: 'SQLBOX', Database name: 'OperationsManagerDW'. Batch ordinal: 5; Exception: Invalid column name 'SchemaName'. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component Instance name: ausp2k3vsrms01.austin.swinc.com Instance ID: {72F573FA-DC50-2534-29D9-5DC6AB18BBE8} Management group: CompanyName

    This is causing the health of my RMS to show up as critical with the “Data Warehouse Database Component Deployment State being the cause.

    Wednesday, December 16, 2009 7:29 PM

Answers

  • Just finished my Reporting Services Upgrade for SCOM 2007 R2 and my issue has been resolved.
    • Marked as answer by Blake Mengotto Thursday, December 17, 2009 9:31 PM
    Wednesday, December 16, 2009 11:00 PM

All replies

  • I am getting a similar error on my SCOM 07 R2 instance as well. Any help would be greatly appreciated.

    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: 'e27ba6b3-43c5-1617-b1e4-29ece3abf589', Management Pack Version-dependent Id: '1a6256f5-34ab-fbb2-4223-8a6ad73a196c'; Target: Database, Server name: '<SQLSERVER>', Database name: 'OperationsManagerDW'. Batch ordinal: 5; Exception: Invalid column name 'SchemaName'.
    Wednesday, December 16, 2009 9:26 PM
  • Found this link:
    http://thoughtsonopsmgr.blogspot.com/2008/11/scom-r2-beta-upgrading-existing-scom.html

    Looks like if you have upgraded to SCOM 07 R2 and not also upgraded reporting services separately, it can generate this error.
    Wednesday, December 16, 2009 9:46 PM
  • Just finished my Reporting Services Upgrade for SCOM 2007 R2 and my issue has been resolved.
    • Marked as answer by Blake Mengotto Thursday, December 17, 2009 9:31 PM
    Wednesday, December 16, 2009 11:00 PM