For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

gbunting's avatar
gbunting
Icon for Nimbostratus rankNimbostratus
Aug 26, 2009

F5 Management pack install fails

I uninstalled the F5 management pack that I was running in order to upgrade to the latest version. The uninstall worked fine. However when I went to install the new management pack I received the following error:

 

 

<08-26-2009 08:03:33> INFO: Changing F5MonitoringService startup type for Distributed Root Management Server to Automatic

 

<08-26-2009 08:03:34> FATALERROR: Health Service could not be started: System.MissingMethodException: Method not found: 'Boolean System.Threading.WaitHandle.WaitOne(System.TimeSpan)'.

 

at F5Networks.ManagementPack.Setup.CustomActionEngine._ChangeServiceState(String serviceName, Boolean start)

 

at F5Networks.ManagementPack.Setup.CustomActionEngine._RunInstall()

 

<08-26-2009 08:03:34> WARNING: Rolling back Installation.

 

<08-26-2009 08:03:34> WARNING: Cannot roll back database changes

 

<08-26-2009 08:03:34> INFO: Removing all temporary files created during install/uninstall

 

 

<08-26-2009 08:03:35> INFO: Removing Windows performance counters.

 

<08-26-2009 08:03:35> FATALERROR: msi failed to run with exit code: 1603

 

<08-26-2009 08:03:35> FATALERROR: Standard error:

 

<08-26-2009 08:03:35> FATALERROR: Standard output:

 

<08-26-2009 08:03:35> FATALERROR: The F5 Networks Management Pack setup has failed.

 

 

Any ideas?

 

 

Attached is the results from the System information script.

 

 

Thanks,

 

 

Glen

2 Replies

  • Stephen_Fisher_'s avatar
    Stephen_Fisher_
    Historic F5 Account
    Hi Glen,

     

     

    Thank you for reporting this.

     

     

    As far as I can tell, the problem occurs on machines that do not have .NET Framework 2.0 SP2 installed. From your SystemInformation log, it looks like you have 2.0 SP1 + a hotfix installed.

     

     

    Can you check your installed version of the .NET Framework?

     

     

    Here are so helpful articles:

     

    Version listing: http://blogs.msdn.com/astebner/archive/2005/07/12/438245.aspx

     

    API Support: http://msdn.microsoft.com/en-us/library/cc189907.aspx

     

     

    If this turns out to be the issue, unfortunately, I don't have a current workaround for you, other than to install a newer .NET Framework (2.0 SP2, 3.0 or 3.5). However, we can investigate removing this dependency in our next release [and only depending on 2.0].

     

     

    Thanks,

     

    Stephen (F5)

     

  • That was it. I didn't realize I needed to upgrade my .NET.

     

     

    Thanks

     

     

    Glen