Forum Discussion

RPriesing_79448's avatar
RPriesing_79448
Icon for Nimbostratus rankNimbostratus
Nov 18, 2009

Error when Enabling monitoring through OpsMgr GUI

When I try to run the task to enable monitoring through the OpsMgr console I get the error below. I can run the command listed in the error from the command prompt with no error. How can we tell if this actually worked?

 

 

 

 

Failed to create process due to error '0x8007010b : The directory name is invalid.', this workflow will be unloaded.

 

 

 

Command executed: "%F5MPPATH%\f5mpcmd.exe" -MonitorHealth:True 10...

 

 

Working Directory: %F5MPPATH%

 

 

 

 

One or more workflows were affected by this.

 

 

 

 

Workflow name: F5.Task_EnableMonitoring

 

 

 

Instance name: bil-lb-dmz01.bil.company.com

 

 

 

Instance ID: {A9825E1B-3D1A-6FE3-32FF-50094B6969C9}

 

 

 

Management group: CORP IT

 

 

Error Code: -2130771918 (Unknown error (0x80ff0032)).

 

management
microsoft
scom
  • Dave_Ruddell_79's avatar
    Dave_Ruddell_79
    Historic F5 Account
    Nov 18, 2009
    I can't say for sure what the issue is yet. We set an environment variable during setup which points to our installation directory. That is the %F5MPPATH% that you are seeing. There is a chance that the Operations Manager console has not picked up this addition, so what you might try is closing and opening the console to refresh the system variables it is using.

     

    That's just my first thought, but let me know if that does not work for you and we'll go from there.

     

     

    Thanks,

     

    -Dave
  • Benjamin_9120's avatar
    Benjamin_9120
    Icon for Nimbostratus rankNimbostratus
    Mar 28, 2010
    I have a same issue in microsoft SCOM console, I have closed and reopen console, but this issue cannot be resolved. why?
  • Dave_Ruddell_79's avatar
    Dave_Ruddell_79
    Historic F5 Account
    Mar 28, 2010
    We've since discovered that the scripts and console tasks are cached in the Operations Manager cache and possibly the database as well. We've updated the WriteActions to look up the installation path instead of use the F5MPPATH variable. This means the only way to fix the issue is to upgrade to the latest version which will overwrite the existing WriteActions and let you run the commands successfully.

     

     

    The other reason this can show up is if you run the task from a Management Server which does not have the F5 Management Pack installed. Because we have other custom software that is installed on the system during setup, if it is not run on each Management Server, not only is the F5MPPATH variable not set, but the libraries and executables required to run any of our tasks will not be available on the server.