Forum Discussion

John_Irving_457's avatar
John_Irving_457
Icon for Nimbostratus rankNimbostratus
Feb 11, 2010

Install of SCOM F5 Man Pack 1.6.2.311 fails

Management Pack 1.5.1.287 will install but will no longer discover devices since 10.1.0 upgrade.

 

 

Management Pack 1.6.2.311 will not install with the following message.

 

 

<02-12-2010 09:09:53> Info: Found .NET framework installed: 2.2.30729

 

<02-12-2010 09:09:54> Info: Started installation of the F5 Networks Management Pack 1.6.2.311.

 

<02-12-2010 09:09:54> Info: msi logging parameters: /lwecma!

 

<02-12-2010 09:09:54> Info: System Center Operations Manager 2007 R2 Reporting Server (Version 6.1.7221.0) found.

 

<02-12-2010 09:09:54> Info: Extracted msi to a temp directory. Running the F5 Networks Management Pack installation.

 

<02-12-2010 09:10:10> Info: Gathering Management Group settings.

 

<02-12-2010 09:10:10> Info: Connecting to Operations Manager Management Group

 

<02-12-2010 09:10:10> Info: Checking to see if Data Warehouse is installed

 

<02-12-2010 09:10:12> Info: Retreiving Data Warehouse Data Source

 

<02-12-2010 09:10:13> Info: Data Warehouse Data Source: Ahsl12

 

<02-12-2010 09:10:13> Info: Retreiving Data Warehouse Initial Catalog

 

<02-12-2010 09:10:13> Info: Data Warehouse Initial Catalog: OperationsManagerDW

 

<02-12-2010 09:10:13> Info: Creating Log on session for user: [adhb.GOVT.NZ\SCOMF5Service]

 

<02-12-2010 09:10:13> Info: Impersonating user: [adhb.GOVT.NZ\SCOMF5Service]

 

<02-12-2010 09:10:13> Info: Opening SQL connection to Data Warehouse

 

<02-12-2010 09:10:13> Info: Changing back impersonation security context

 

<02-12-2010 09:10:13> FatalError: An unexpected fatal error has occurred during the F5 Networks Management Pack Setup. Please contact the F5 Management Pack team at managementpack@f5.com with the following information: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)

 

at System.String.Format(IFormatProvider provider, String format, Object[] args)

 

at F5Networks.Globalization.StringManager.GetFormattedString(ResourceCategory category, String id, String[] replacementStrings)

 

at F5Networks.ManagementPack.Setup.SetupHarness._MakeSqlDataWarehouseCheck(String dataWarehouseDataSource, String dataWarehouseInitialCatalog, SetupLogger setupLog)

 

at F5Networks.ManagementPack.Setup.SetupHarness._ValidateReadDataWarehouse(String serviceAccount, String servicePassword, String serviceDomain, SetupLogger setupLog)

 

at F5Networks.ManagementPack.Setup.SetupHarness._RunMsi(Boolean debugHelper, Boolean quietInstall, Boolean guiInstall, Boolean existingInstall, Boolean& uninstall, Boolean& upgrade, Boolean canUpgrade, Boolean& repairInstall, Boolean& installSuccess, SetupLogger setupLog, String& sqlServer, String& sqlUser, String& sqlPassword, String& serviceAccount, String& servicePassword, String& serviceDomain, String& rmsServer, String& installDirectory, String msiLogType, String msiLogFile, String msiHelperLogFile, String msiFileName, String installTime, String registrationKey, Boolean forceReg, Version ManagementPackVersion, Boolean& serviceRunning, SetupUI setupGui, Boolean debugLogging, Boolean isOpsMgrR2)

 

at F5Networks.ManagementPack.Setup.SetupHarness._Main(String[] args, SetupLogger& setupLog, Boolean& quietInstall)

 

at F5Networks.ManagementPack.Setup.SetupHarness.Main(String[] args)

 

management
microsoft
scom
  • Dave_Ruddell_79's avatar
    Dave_Ruddell_79
    Historic F5 Account
    Feb 11, 2010
    Hey John,

     

     

    Sorry for the problems you are running into. The error you found is a slight bug in our installer code; however, it still reveals the real problem, which is the user account: adhb.GOVT.NZ\SCOMF5Service not being able to connect to the SQL database OperationsManagerDW on server Ahsl12. Can you verify that the user has at least read permissions on the database in question.

     

     

    Better yet, if you log in as the user, you can try and run the following SQL query to manually ensure things are set up correctly.

     

    SELECT TOP 1 
     et.ManagementPackRowId 
 FROM 
     vManagedEntityType et with (nolock)

     

     

    If you are able to get this query to work for the SCOMF5Service user, you should be able to run Setup again successfully. Sorry for the inconvenience, and let us know how this turns out.

     

     

    Thanks,

     

    -Dave
  • John_Irving_457's avatar
    John_Irving_457
    Icon for Nimbostratus rankNimbostratus
    Feb 14, 2010
    The OpsManagerDW is not on Ahsl12.

     

     

     

    The RMS is AHSL12 & this is where I am trying to install the F5 Management pack.

     

     

    Ahsl20 is the SQL server where all the databases are installed.

     

     

    SCOMF5Service is local admin on Ahsl12 & sa on Ahsl20.

     

     

    I am also getting failed login attempts on Ahsl12 (SCOM RMS) Server even though the setup wizard asks where the SQL server is & I specify Ahsl20.

     

     

    On the old version I also got this but the installer was able to continue.

     

  • Dave_Ruddell_79's avatar
    Dave_Ruddell_79
    Historic F5 Account
    Feb 15, 2010
    John,

    I am starting to suspect something strange is going on. The way we get the Ahsl20 server is by directly querying this information from the SCOM administration. If this is returning the wrong SQL server, then I think there might be something wrong with SCOM or your deployment. We can verify this a couple of ways:

    PowerShell way:

    1. Open up an Operations Manager PowerShell console.

    2. Enter the following commands: 
    $mgc = Get-ManagementGroupConnection;  
  $mg = $mgc.ManagementGroup;  
  $mga = $mg.GetAdministration();  
  $dwsn = [Microsoft.EnterpriseManagement.Administration.Settings+ManagementGroup+DataWarehouse]::DataWarehouseServerName;  
  $mga.Settings.GetDefaultValue($dwsn);

    3. Report back value returned by last statement in the script above.

    Registry way:

    1. Start RegEdit

    2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting

    3. Report back value of DWDBInstance and DWDBName

    Also, during our Setup program, the SQL server it wants you to specify is where the F5 DB will live, not necessarily where the OpsMgr DBs are. It finds the OpsMgr SQL Server and uses that as the default value since we know there is a ‘related’ database at that location.

    If these 2 values do not match, we have a problem, or if they are not what you expect them to be. But let us know and we'll help you figure out how to resolve it.

    Thanks,

    -Dave
  • John_Irving_457's avatar
    John_Irving_457
    Icon for Nimbostratus rankNimbostratus
    Feb 16, 2010
    Thanks.

     

     

    This is the RegKey setting.

     

     

    Ahsl20

     

     

     

     

     

    It appears the PowerShell returns something different...

     

     

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    >$mgc = Get-ManagementGroupConnection

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    >

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    > $mg = $mgc.ManagementGroup

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    >

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    > $mga = $mg.GetAdministration()

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    >

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    > $dwsn = [Microsoft.EnterpriseManagement.Administration.Settings+ManagementGroup+Da

     

    taWarehouse]::DataWarehouseServerName

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    >

     

    PS Monitoring:\ahsl12.adhb.govt.nz

     

    > $mga.Settings.GetDefaultValue($dwsn)

     

    Ahsl12

     

  • joel_hendrickso's avatar
    joel_hendrickso
    Historic F5 Account
    Feb 16, 2010
    John,

     

     

    It looks like your data warehouse may have been moved at some point -- is that the case?

     

     

    I have a couple diagnostics you can run and hopefully a fix as well. You will need to run some SQL queries against the Operations Manager database:

     

     

    1. Open SQL Server Management Studio

     

    2. Connect to the Operations Manager operational database server

     

    3. Expand the databases to the OperationsManager database and select that database

     

    4. Click the "New Query" button in the top left

     

    5. Paste the following queries into the window and then click "Execute":

     

     

     

    -- Get the global setting

     

    select SettingValue

     

    from globalsettings G

     

    join managedtypeproperty MTP on G.managedtypepropertyid = MTP.managedtypepropertyid

     

    join managedtype MT on MTP.managedtypeid = MT.managedtypeid

     

    where typename = 'Microsoft.SystemCenter.DataWarehouse'

     

    and ManagedTypePropertyName = 'MainDatabaseServerName'

     

     

    -- Get the instance setting

     

    select MainDatabaseServerName_16781F33_F72D_033C_1DF4_65A2AFF32CA3 from MT_DataWarehouse

     

     

     

    I'm guessing that the second query will return the correct data warehouse server and that the first query will be empty or wrong. To correct the first value (if it is wrong), stop the SCOM services (System Center Data Access, System Center Management, System Center Management Configuration) and then run this query in the same way as the previous queries:

     

     

     

    update GlobalSettings

     

    set SettingValue = 'CORRECT DATA WAREHOUSE SERVER NAME HERE'

     

    from globalsettings G

     

    join managedtypeproperty MTP on G.managedtypepropertyid = MTP.managedtypepropertyid

     

    join managedtype MT on MTP.managedtypeid = MT.managedtypeid

     

    where typename = 'Microsoft.SystemCenter.DataWarehouse'

     

    and ManagedTypePropertyName = 'MainDatabaseServerName'

     

     

     

    Please send the results of the first two queries as this will help improve our product.

     

     

     

     

  • joel_hendrickso's avatar
    joel_hendrickso
    Historic F5 Account
    Feb 16, 2010
    John -- Just wanted to emphasize that in the query to fix the data warehouse value, make sure the replace 'CORRECT DATA WAREHOUSE SERVER NAME HERE' with your data warehouse server ('Ahsl20 ' I believe).
  • John_Irving_457's avatar
    John_Irving_457
    Icon for Nimbostratus rankNimbostratus
    Feb 16, 2010
    Yes the datawarehouse was moved to a dedicated SQL server.

     

     

    -- Get the global setting

     

    select SettingValue

     

     

    AHSL12 (This is the RMS server)

     

     

    -- Get the instance setting

     

    AHSL20 (This is the SQL server)

     

     

    I ran the upgrade script & then the installer worked fine & I was able to discover the F5 devices.

     

     

    This is now working.

     

    Thank you for your assistance.

     

     

    I have never dealt with a support process that provided such an accurate assesment of the issue & such a targeted fix. Once again Thank you.

     

     

    Cheers

     

     

    John