How do I change the severity level for jobs that abort so that it does not trigger a critical error? (NETIQKB10076)

  • 7710076
  • 02-Feb-2007
  • 12-Jan-2011

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

How do I change the severity level for jobs that abort so that it does not trigger a critical error?

Resolution

To modify the default event severity used when a job is ABORTED a change needs to be made to the registry on the AppManager Management Server the following steps should be taken.

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. NetIQ cannot guarantee that problems resulting from the incorrect use of Registry Editor can be resolved. Make sure that you backup your Registry prior to making any changes.

  1. Using a registry editor (regedit or regedt32) navigate to:
    hkey_local_machine>software>netiq>appmanager>4.0>NetIQms>Config
  2. Modify the following registry key:
    MC Job Abort Event Sev
  3. By default it is set to hex "a" which equates to a severity level of "10." Change this value to the severity level desired. 
    For example = a desired severity value of "21" would equate to a "hex 15," so the new value would be displayed as "0x15" in the registry.
    To enter in this value, users must choose DECIMAL and not HEX when entering in the new value into the registry.
  4. After making the change to the registry, please stop and restart the NetIQ AppManager Management Server service for the changes to take effect.
    Please note: T his is a GLOBAL change and not on an individual knowledge script basis.

Additional Information

Formerly known as NETIQKB10076

An ABORTED job is different from a job that generates an Event. If a job aborts it can be for a variety of reasons ranging from changes to a user's hardware/software on a system, failed devices, etc.