SCOM 2007 R2報表安裝時會停住不動 RRS feed

  • 問題

  • 各位好,小弟安裝的環境如下:


    系統:WINDOWS 2008 R2


    目前已安裝SCOM 2007 R2並可正常收到各主機回傳的相關資料,但在安裝報表時,卻卡下面的畫面不動(按完下一步就像程式當掉一樣不會動也不能按),有重新將作業系統及SCOM 2007 R2整個重新安裝,但問題依舊,試著用TOOLS將資料倉儲的資料庫手動建立後,再安裝報表,仍然是卡在下面這個畫面,不知道各位有沒有遇過相同的問題。


    2011年10月6日 上午 04:20



  • 是要將作業系統升級到SP1的版本安裝就正常了。
    • 已標示為解答 Richman3030 2011年10月18日 上午 08:35
    2011年10月18日 上午 08:35
  • Hi, Richman3030:

         我有類似的問題, 找到了相關的資料, 你應該會有需要或是興趣, 已經解決了嗎


    Deploying Reporting in the Single Server, Single Management Group Scenario

    Updated: May 22, 2009

    Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

    In this scenario, the SQL Reporting Services database and the Operations Manager Data Warehouse database are installed in the same instance of SQL Server as the Operations Manager database.

    During this installation, you are prompted for two accounts: the Data Warehouse Write account and the Data Reader account. These accounts are created as domain user accounts and added to the local Administrators group on the target server.

    • Data Warehouse Write account: This account is assigned write permissions on the Data Warehouse database and read permissions on the Operations Manager database.
      Before you perform this procedure, be sure that the account you plan to use for the Data Warehouse Write Account has SQL Login rights and is an Administrator on the computers hosting both the Operations Manager database and Reporting data warehouse. Otherwise, setup will fail and all changes will be rolled back. This might leave SQL Reporting Services in an inoperable state.
  • Data Reader account: This account is used to define which account credentials SQL Reporting Services uses to run queries against the Operations Manager Reporting Data Warehouse. This account is also used for the SQL Reporting Services IIS application pool account to connect to the RMS.

    The account that you use to run the Operations Manager 2007 R2 Reporting installation must be a member of the following groups and roles.

    • Local Administrator – this is required by the Operations Manager 2007 R2 Reporting installation and for configuring SQL Server Reporting Services.

    • Operations Manager Administrator role – this is required for configuring reporting roles.

    • SQL SysAdmin for the Operations Manager database – this is required for configuring dwsynch_users role.

    • SQL SysAdmin for the Data Warehouse database – this is required for configuring OpsMgrWriter and OpsMgrReader roles.

    Installing Operations Manager 2007 R2 Reporting Single Server Configuration

    To install Operations Manager 2007 R2 Reporting

    1. Ensure that SQL Server Reporting services has been correctly installed and configured. For more information about installing and configuring SQL Server 2005 Reporting services see<sup>1</sup>; for SQL Server 2008 Reporting services see<sup>2</sup>.

    2. For a listing of the top 10 Reporting Services installation issues and their resolutions see<sup>3</sup>

    3. On the server that you are going to install Operations Manager on, log on with the Operations Manager Administrator account.

    4. On your installation media, run SetupOM.exe to start the System Center Operations Manager 2007 R2 Setup wizard.

    5. Under the Install heading, click Install Operations Manager 2007 R2 Reporting.

    6. On the Welcome page, click Next.

    7. On the End-User License Agreement page, read the license agreement, select I accept the terms in the license agreement, and then click Next.

    8. On the Product Registration page, enter the appropriate values in the User Name and Organization fields, and then click Next.

    9. On the Custom Setup page, ensure that the Data Warehouse and Reporting Server components are set to This component, and all dependent components, will be installed on the local disk drive, and then click Next.

      If you specify a custom name for the Data Warehouse database, be sure not to include a '-' character. The database installation will fail if a '-' character is included in the name.

    10. On the Connect to the Root Management Server page, enter the name of the first server in the management group. In this case, it is the server that you are installing Operations Manager on. Click Next.

    11. On the SQL Server Database Instance page, select the SQL Server database instance from the drop-down list. This drop-down list contains the SQL Server database instance name that was created when you installed SQL Server 2005 or SQL Server 2008 and should be the name of the server that you are installing Operations Manager 2007 R2 on. Accept the SQL Server Port default (1433) or modify it if you have configured SQL to use a different port. Click Next.

    12. On the Database and Log File Options page, you can accept the default value of OperationsManagerDW for the SQL Database Name, or you can enter a different name. It is recommended that you accept the default value. Enter an appropriate value in the Database size field or accept the default 1000 MB.

      If you choose to use custom directories for the OperationsManagerDW data and log files, you must create these custom directories prior to starting the setup process for the OperationsManagerDW.

    13. The Data file location and Log file location boxes indicate where the database and log files will be installed. The default is the installation directory of SQL Server on the computer. If you have created additional partitions or drives to allow the separation of the database files and the log files, click Advanced to enter the appropriate drive, path and folder names. Otherwise, click Next.

    14. On the SQL Server Reporting Services Instance page, select the Reporting Services server instance name from the drop-down list. The server name should already be selected. Click Next.

      Installing Operations Manager 2007 R2 Reporting Services integrates the security of the SQL Reporting Services instance with the Operations Manager role-based security. Do not install any other Reporting Services applications in this same instance of SQL Server Reporting Services.

    15. On the Data Warehouse Write Account page, enter the Data Write account credentials, and then click Next.

    16. On the Data Reader Account page, enter the Data Reader account credentials, and then click Next.

    17. On the Operational Data Reports page, indicate whether you want to send data reports to Microsoft, and then click Next.

    18. On the Ready to Install the Program page, click Install when you are ready for the installation to proceed.

    19. After setup completes, the Setup wizard displays the Completing the Operations Manager Reporting Components Setup Wizard page. Click Finish.

    Confirming the Health of Reporting Services

    Operations Manager Reports are accessed in the Operations console, in the Reporting view. After initial deployment, it takes up to 30 minutes for reports to appear.

    To confirm the health of Operations Manager Reports

    1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 R2 management group.

    2. Select the Reporting view.

    3. Click Microsoft ODR Report Library, and then double-click any of the reports listed; by default, you should see the management group, management packs and Most Common Alerts reports. The selected report will then generate and display in a new window.

      Selecting the management packs report is particularly useful at this point because it provides you with a full inventory of the management packs that have been installed on your server.

    4. Close the report window.

    希望對你有幫助, 光是把Windows 2008 Server R2 升級到SP1 不會解決問題.

2012年3月13日 下午 03:45