Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you try to generate a report in System Center Operations Manager 2007: "Cannot initialize report"

Error message when you try to generate a report in System Center Operations Manager 2007: "Cannot initialize report"

Symptoms

When you run Microsoft System Center Operations Manager 2007, you experience the following symptoms:
  • When you try to generate a report by using a link in a view in the Operations Manager 2007 Operations Console, you receive the following error message:
    Application: System Center Operations Manager 2007

    Application Version: 6.0.5000.0

    Severity: Error

    Message: Cannot initialize report.

    Microsoft.Reporting.WinForms.ReportServerException: The item

    '/Microsoft.SystemCenter.DataWarehouse.Report.Library/Microsoft.SystemCenter.DataWar
    ehouse.Report.Alert' cannot be found. (rsItemNotFound)

    at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo()

    at Microsoft.Reporting.WinForms.ServerReport.GetParameters()

    at

    Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterB lock.Initialize(ServerReport serverReport) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Objec t sender, ConsoleJobEventArgs args)
  • When you try to view a report by using the Reporting node in the Operations Manager 2007 Operations Console, no unpublished reports appear.
  • The following events may be logged in the Operations Manager log on the management server.Note Event ID 11411 is logged every 10 minutes.

↑ Back to the top

Cause

This problem occurs if the data warehouse database was created by using the DBCreateWizard tool. The DBCreateWizard tool is located on the Microsoft System Center Operations Manager 2007 media.

To determine whether you experience the problem that is described in the "Symptoms" section, follow these steps:
  1. On the data warehouse database server, start the Microsoft SQL Server Management Studio program.
  2. Click New Query, and then click OperationsManagerDW in the list that appears in the standard toolbar.

    Note If the database that houses the data warehouse is not OperationsManagerDW, click the appropriate database.
  3. Type the following query, and then press F5 to run the query:
    Select * from MemberDatabase
    Note This query is used to determine whether required information is missing from the database.
  4. Examine the results that are returned.


    If this query returns no rows in the query results, you are experiencing the problem that is described in this article. In this scenario, continue to the "Resolution" section.

    If this query returns rows in the query results, and if the server name is returned in the query results, you are not experiencing the problem that is described in this article. Instead, you may be experiencing a SQL Server permissions-related issue. In this scenario, do not follow the steps in the "Resolution" section.

↑ Back to the top

Resolution

To resolve this problem, follow these steps:
  1. On the data warehouse database server, start the Microsoft SQL Server Management Studio program.
  2. Click New Query, and then click OperationsManagerDW in the list that appears in the standard toolbar.

    Note If the database that houses the data warehouse is not OperationsManagerDW, click the appropriate database.
  3. Type the following query, and then press F5 to run the query:
    EXEC MemberDatabaseAttach 'dbserver\instanceName', 'datawarehouseDBname', 1, 1, 1


    Note In this query, replace dbserver\instancename with one of the following:
    • If you do not use the default instance of SQL Server, replace dbserver\instancename with the NetBIOS name of the computer that is running SQL Server together with the name of the instance of SQL Server. For example, replace dbserver\instancename with DWServer\Instance-1.
    • If you use a default instance of SQL Server, replace dbserver\instancename with only the NetBIOS name of the computer. For example, replace dbserver\instancename with DWServer.
  4. To verify that the table has been updated successfully, delete the contents of the query window, type the following query, and then press F5 to run the query:
    Select * from MemberDatabase
If the table is updated successfully, one row is returned in the query results. For example, the query results may resemble the following.
MemberDatabaseRowIdServerNameDatabaseNameMasterDatabaseIndDefaultDatabaseIndComponentAutoDeploymentAllowedIndMasterDatabaseReferenceServerNameMasterDatabaseReferenceDatabaseName
DWServerOperationsManagerDW111NULLNULL
Note After you follow these steps, several Event ID 31554 events may be logged in the Operations Manager log on the management server. These events have the following Description information:

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kberrmsg, kbtshoot, kbentirenet, kbprb, kb

↑ Back to the top

Article Info
Article ID : 942865
Revision : 3
Created on : 9/10/2018
Published on : 9/10/2018
Exists online : False
Views : 110