Forum Discussion

Gordon_O_138935's avatar
Gordon_O_138935
Icon for Nimbostratus rankNimbostratus
Dec 03, 2013

Monitoring Pack Install on 2012R2 with OpsMgr 2012 R2 Failing

Working in my lab environment I have been trying to get the Monitoring Pack to successfully load. Using the executable to perform the load and providing correct information for the SQL server as well as a valid id for the service account the application fails due to an command line error with the msi. Below is a portion of the log file, I did verify that the registry entry for .NET 4 are there.

 

Any help would be appreciated on this.

 

Gordon

 

<12-03-2013 11:40:10> Warning: Could not find System Center Operations Manager R2 Hotfix KB981740 or the System Center Operations Manager 2007 R2 Cumulative Update 3. To obtain the hotfix or update, please visit one of the sites below: Database Hotfix: http://support.microsoft.com/KB/981740 Cumulative Update 3: http://support.microsoft.com/KB/2251525 <12-03-2013 11:40:10> Warning: Could not locate the .NET Framework Version value from registry Key CDF. Setup was attempting to access information from the registry hive HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP <12-03-2013 11:40:10> Info: Found .NET framework installed: v3.0 SP <12-03-2013 11:40:10> Info: Found .NET framework installed: v3.5 SP <12-03-2013 11:40:10> Warning: Could not locate the .NET Framework Version value from registry Key v4. Setup was attempting to access information from the registry hive HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP <12-03-2013 11:40:10> Warning: Could not locate the .NET Framework Version value from registry Key v4.0. Setup was attempting to access information from the registry hive HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP <12-03-2013 11:40:10> Info: Started installation of the F5 Networks Monitoring Pack 3.2.1.175. <12-03-2013 11:40:10> Info: msi logging parameters: /lwecma! <12-03-2013 11:40:10> Info: System Center Operations Manager 2012 Server (Version 7.1.10226.0) found. <12-03-2013 11:40:10> Info: Extracted msi to a temp directory. Running the F5 Networks Monitoring Pack installation. <12-03-2013 11:40:46> Info: Installation path: C:\Program Files\F5 Networks\Management Pack\ <12-03-2013 11:40:46> Info: Command Line Arguments: /sva:svcxxxxxxxx /svp:xxxxxxxx /svd:US /log:C:\Program Files\F5 Networks\Management Pack\log\setup.log /dir:C:\Program Files\F5 Networks\Management Pack\ /sql:uslabopss01\opsmgr2012 /su: <12-03-2013 11:40:46> Info: Temporary Directory: C:\Users\xxxxx\AppData\Local\Temp\F5 Networks\Management Pack\20131203_114046 <12-03-2013 11:40:46> Info: installing F5 Networks Monitoring Pack <12-03-2013 11:40:46> Info: Installing Windows performance counters. <12-03-2013 11:40:54> Info: Windows performance counters successfully installed. <12-03-2013 11:41:22> Info: Removing Windows performance counters. <12-03-2013 11:41:24> Info: Windows performance counters removed successfully. <12-03-2013 11:41:24> FatalError: msi failed to run with exit code: 1639

 

1 Reply

  • because this was a lab environment, i just nuked the whole setup and started from scratch. the install went ok the second time around.