This article has been archived. It is offered "as is" and will no longer be updated.
When you try to install a secondary management server in a management group on which a Microsoft System Center Operations Manager 2007 Reporting server has been installed, the installation rolls back. When the AddRunAsProfilesCA custom action runs, the following appears in the MSI installation log:
AddRunAsProfilesCA: Error: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index, Stack: at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) at System.ThrowHelper.ThrowArgumentOutOfRangeException() at System.Collections.Generic.List`1.get_Item(Int32 index) at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfile(String profleGuid, MonitoringObject hostedHealthService, ManagementGroup managementGroup, String currentActionUserDomain, String currentActionUserName) at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfiles(Session session)
This problem occurs because the Data Warehouse Write Action account was the same as the Root Management Server (RMS) Action account when you installed System Center Operations Manager 2007 Report Server. If these accounts are the same when you install Report Server Service Pack 1, Report Server does not create a Datawarehouse Action account as a data warehouse collection. Additionally, synchronization rule workflows run under the RMS action account.
When you install a secondary management server role, Report Server interrogates the Data Warehouse Account profile. When Report Server determines that the Data Warehouse Account profile is empty, the installation failure occurs.
To resolve this problem in Operations Manager 2007 and in Operations Manager 2007 SP1, follow these steps to install a secondary management server role:
In the System Center Operations Manager console, locate the Administration space.
Under Security, select Run As account, and then create a new Windows Run As account. For example, you can create an account that is named "Data Warehouse Action Account." Provide the same user name and password that the default action account uses.
Associate the new Run As account to the “Data Warehouse Account” Run As profile.
Associate the new Run As account to the “DW Configuration and Synchronization Reader Account” Run As profile. To do this, locate the Run As Profiles list, and then locate the Run As profile that is named "Reserved." Typically, you see three of these Run As profiles. In the Run As Profile Properties dialog box, locate the profile that contains Data Warehouse Library in the Select destination management pack list. Add the new Run As Account, "Data Warehouse Action Account," to this profile.
To work around this problem in Operations Manager 2007 R2, contact Microsoft Customer Support Services.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.