IBM Support

IT16553: Windows application event log not being populated with MQ messages

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • IBM MQ logs errors and informational messages in the Windows
    Application Event Log but in V9 this was broken and the
    following message was recorded for all messages:
    
    The description for Event ID <1234> from source
    IBM MQ <Installation_name> cannot be found. Either the
    component that raises this event is not installed on your
    local computer or the installation is corrupted. You can
    install or repair the component on the local computer.
    

Local fix

  • Modify the name of MQ from Websphere MQ to IBM MQ at the
    following place in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Ap
    plication\WebSphere MQ ()
    
    For example if the the installation name for a version 9
    is "Installation2" then change the entry to:
    
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Ap
    plication\IBM MQ (Installation2)
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ V9 on Windows
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The error messages were not written to the Windows application
    event log due to a wrongly configured registry key.
    

Problem conclusion

  • The installation code is fixed such that right registry key
    entries are created.
    
    
    Please note that because this issue exists in the product
    installation code, it can only be addressed for 9.0.0.0
    installations by uninstalling MQ and re-installing a full
    product installer level which contains the fix, or by performing
    the steps described above in the local fix section.
    
    This issue cannot be resolved by the application of an MQ fix
    pack.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.1
    v9.0 LTS   9.0.0.1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT16553

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-10

  • Closed date

    2016-11-11

  • Last modified date

    2017-06-28

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 June 2017