IBM Support

IZ20712: CHECK WHICH WINDOWS SERVICES THAT ARE USING WMI ARE RUNNING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If restart WMI is enabled, it attempts to also start all
    dependent services, whether they were up or running or not.
    Chris L. thought we could potentially check and save the status
    of each dependent service before we stop WMI and then only
    start those services that were running before the WMI stop, if
    they are stopped afterwards.   Another option is to possibly
    use "net stop winmgmt /y" and then capture what else is stopped
    so it can be restarted later.
    

Local fix

  • change the collation.properties parameters to not restart wmi
    

Problem summary

  • If WMI restart is enabled, check which windows services that are
    using WMI are running before
    stopping them and only start those that were started beforehand.
    TADDM relies on WMI to discover Windows
    Operating Systems.  If a problem is encountered with WMI TADDM
    may restart the WMI service.
    
    Note that any service dependent on WMI will also be restarted if
    the WMI service is restarted.
    
    These restarts are controlled by the following
    collation.properties settings.  The default value is for
    WMI restart is true as this provides more reliable Windows
    discovery.
    
    Note that if automatic restart is disabled, discovery of Windows
    targets may fail if WMI fails to respond as expected.
    
    # Restart WMI if a WMI error is encountered during AutoDeploy
    com.collation.RestartWmiOnAutoDeploy=true
    com.collation.RestartWmiOnAutoDeploy.1.2.3.4=true
    
    # Restart WMI if a WMI error is encountered (except during
    AutoDeploy)
    com.collation.RestartWmiOnFailure=true
    com.collation.RestartWmiOnFailure.1.2.3.4=true
    

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenance packages:
    | Interim Fix | 7.1.0.0-TIV-ITADDM-IF0005
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ20712

  • Reported component name

    APP DEPENDENCY

  • Reported component ID

    5724N5500

  • Reported release

    511

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-21

  • Closed date

    2008-05-30

  • Last modified date

    2008-05-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    APP DEPENDENCY

  • Fixed component ID

    5724N5500

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"511","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 May 2008