Common WebSphere MQ messages and most likely causes

Technote (troubleshooting)


Problem(Abstract)

You want to understand the reason for the most common WebSphere MQ error messages.

Resolving the problem

This document contains a listing of common MQ error messages and explains the most likely reason for the error. There can be many reasons for each of these messages, however this is our attempt to help you understand the most probable cause, and lead you to the most recent troubleshooting documents for a quick solution.
Click on the error message that you are getting

Common WebSphere messages
AMQ4036
AMQ4100
AMQ4128
AMQ4757
AMQ6090
AMQ6119
AMQ6125
AMQ6150
AMQ6183
AMQ6184
AMQ7469
AMQ8101
AMQ9202
AMQ9208
AMQ9209
AMQ9213
AMQ9228
AMQ9503
AMQ9526



AMQ4036 Access not permitted. You are not authorized to perform this operation.

Explanation:
The queue manager’s security mechanism has indicated that the userid associated with this request is not authorized to access the object.

The Remote Administration connection is initiated by a user on a Windows machine and the user is attempting to connect to a remote queue manager, so it can remotely administer MQ objects. The attempt is failing because the initiator user ID does not have the authority to access one or more objects on the remote system.

Most common cause:
The Windows user ID:

  • not defined on the remote machine
  • not defined correctly (case matters)
  • longer that 12 characters (restriction in some OS environments)
  • does not have enough authority to access remote objects

Diagnostic hints and tips:
The easiest way to resolve this problem is to make the Windows user ID a super user on the local and remote systems. The user should have full authority and access to all MQ objects on the remote system. Make this user a member of the "mqm" group in the OS environments that have an "mqm" group defined.
    Additional information:
    Ensure that you have satisfied the following requirements before trying to use the WebSphere MQ Explorer to do remote administration. Verify that:
    1. The WebSphere MQ server and client is installed on the local and the remote machine.
    2. A command server is running for every queue manager.
    3. A TCP/IP listener exists for every queue manager. This can be the WebSphere MQ listener, or the inetd daemon in as appropriate.
    4. The server-connection channel, called SYSTEM.ADMIN.SVRCONN, exists on every remote queue manager. This channel is mandatory for every remote queue manager being administered. Without it, remote administration is not possible. You can create the channel using the following MQSC command: DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
    5. The user ID of the initiator on Windows machine must be a member of the "mqm" group on the remote machine.
    6. WebSphere MQ V6.0 requires the model queue SYSTEM.MQEXPLORER.REPLY.MODEL. You can create the queue using the following MQSC command: DEFINE QMODEL(SYSTEM.MQEXPLORER.REPLY.MODEL)

    Click here for most recent troubleshooting documents


    AMQ4100 The MMC document file <filename> could not be created. The IBM WebSphere MQ Services console has failed to initialize.

    Explanation:
    The service program has attempted to create a default MSC document file in the MQM\bin directory, but could not.

    User Response:
    Check that the disk is not full, and that the user has create and write permissions in the MQM bin directory.

    Most common causes:

    • MUSR_MQADMIN user ID not created due to user input during installation
    • MUSR_MQADMIN user ID does not have permission to access a Registry Entry
    • MUSR_MQADMIN user ID password was changed

    Diagnostic hints and tips:
    • Run the following commands to reregister the MQ Service and the proxy:
      amqmsrvn -regserver
      regsvr32 amqmspsn.dll
    • Add the MUSR_MQADMIN to the administrators group

    Click here for most recent troubleshooting documents


    AMQ4128 Could not start the iKeyMan program.

    Explanation:
    An error was encountered when trying to execute the iKeyMan program.

    Click here for most recent troubleshooting documents


    AMQ4757 IBM WebSphere MQ files are in use. Stop activity and retry

    Explanation:
    One or more WebSphere MQ files are being used by processes running on the system.

    Response:
    Ensure that all queue managers, listeners, channels and WebSphere MQ services are stopped. Use the Windows task manager to ensure that there are no processes running with an amq*, runmq*, or strmq* prefix. Stop any tools used to monitor WebSphere MQ and stop any Performance Monitor tasks. If the process locking WebSphere MQ files cannot be identified, installation can usually proceed following a reboot, with the WebSphere MQ service disabled.

    Most common cause:
    The MQSeries install fails because the MQ DLL's are being used.

    Diagnostic hints and tips:
    You can set an installation parm that will allow the installation to complete, even if MQ DLL's are being used. For details see APAR IC57153.

    Click here for most recent troubleshooting documents


    AMQ6090 WebSphere MQ was unable to display an error message <insert_6>

    Explanation:
    MQ has attempted to display the message associated with return code hexadecimal <insert_6>. The return code indicates that there is no message text associated with the message. Associated with the request are inserts <insert_1> : <insert_2> : <insert_3> : <insert_4> : <insert_5>.

    Response:
    Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

    Most common cause:

    • This can occur if the message catalog is missing or corrupted
    • This can be observed on Linux distributions, that use NPTL threading, when the environment variable LD_ASSUME_KERNEL is not set.

    Diagnostic hints and tips:
    • Copy the amq.cat file from another MQSeries installation (at the same MQ version) that is not having the problem
    • WebSphere MQ 5.3 in Linux requires the following environment variable, before installing the product, creating/starting a queue manager or before issuing any MQ command: export LD_ASSUME_KERNEL=2.4.19
    • Increase the number of file descriptors

    Click here for most recent troubleshooting documents


    AMQ6119 An internal WebSphere MQ error has occurred (<insert_3>)

    Explanation:
    MQ detected an unexpected error when calling the operating system. The MQ error recording
    routine has been called.

    Response:
    Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

    Most common cause:
    This error can is raised for many reasons, it is a very generic error message.

    Diagnostic hints and tips:

    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination.

    Click here for most recent troubleshooting documents


    AMQ6125 An internal WebSphere MQ error has occurred

    Explanation:
    An internal error has occurred with identifier <insert_1>. This message is issued in association with other messages.

    Response:
    Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

    Most common cause:
    This error can is raised for many reasons, it is a very generic error message.

    Diagnostic hints and tips:

    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination.


    Click here for most recent troubleshooting documents


    AMQ6150 (Windows) WebSphere MQ semaphore is busy

    Explanation:
    WebSphere MQ was unable to acquire a semaphore within the normal timeout period of <insert_1> minutes.

    Response:
    MQ will continue to wait for access. If the situation does not resolve itself and you suspect that your system is locked then investigate the process which owns the semaphore. The PID of this process will be documented in the accompanying FFST.

    Most common cause:
    Applications ending normally or abnormally without disconnecting for MQSeries

    Diagnostic hints and tips:

    • Ensure that all applications disconnect from MQSeries before ending.
    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination.

    Click here for most recent troubleshooting documents


    AMQ6183 An internal WebSphere MQ error has occurred

    Explanation:
    An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process <insert_1>.

    Response:
    Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

    Most common cause:
    This it is a very generic error that informs you that another process has failed. Use the process number in the message insert to correlate it with the FFDC record for the failing process.

    Diagnostic hints and tips:

    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination.


    Click here for most recent troubleshooting documents


    AMQ6184 An internal WebSphere MQ error has occurred on queue manager <insert_3>

    Explanation:
    An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process <insert_1>.

    Response:
    Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

    Most common cause:
    This it is a very generic error that informs you that another process has failed. Use the process number in the message insert to correlate it with the FFDC record for the failing process.

    Diagnostic hints and tips:

    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination


    Click here for most recent troubleshooting documents


    AMQ7469 Transactions rolled back to release log space

    Explanation:
    The log space for the queue manager is becoming full. One or more long-running transactions have been rolled back to release log space so that the queue manager can continue to process requests.

    Response:
    Try to ensure that the duration of your transactions is not excessive. Consider increasing the size of the log to allow transactions to last longer before the log starts to become full.

    Most common cause:
    The size of the log depends primarily upon the duration of the longest running Unit Of Work (UOW) and the throughput on the log. When the log starts to become full, then the queue manager will start backing out long running transactions and penalizing (performance) heavy log users.

    Diagnostic hints and tips:

    • You can avoid this problem by committing Units Of Work (UOWs) more frequently.
    • Increase the number of log files.
      This can be done with the system running and will require a queue manager restart.
        Windows:
        Use the MQServices MMC to increase the number of Files.
        UNIX and Linux:
        1. Edit the /var/mqm/qmgrs/{QMgrName}/qm.ini file. Increase the value of the LogPrimaryFiles & LogSecondaryFiles. The sum of both have to be less than or equal to 63 (V5.3) 511(V6.0)
        2. Stop the QueueManager
        3. Restart QueueManager
    • Increase the size of the log files.
      This method requires you to delete and redefine the queue manager with larger log file sizes.

    Click here for most recent troubleshooting documents


    AMQ8101 WebSphere MQ error (<insert_1>) has occurred

    Explanation:
    An unexpected reason code with hexadecimal value <insert_1> was received from the WebSphere MQ queue manager during command processing. (Note that hexadecimal values in the range X’07D1’-X’0BB7’ correspond to MQI reason codes 2001-2999.) More information might be available in the log. If the reason code value indicates that the error was associated with a particular parameter, the parameter concerned is <insert_4>.

    Response:
    Correct the error and then try the command again.

    Most common cause:
    This is a serious error that usually prevents you from starting or creating a queue manager.

    Diagnostic hints and tips:

    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination

    Click here for most recent troubleshooting documents


    AMQ9202 Remote host <insert_3> not available, retry later

    Explanation:
    The attempt to allocate a conversation using <insert_4> to host <insert_3> was not successful. However the error may be a transitory one and it may be possible to successfully allocate a <insert_4> conversation later.

    Response:
    Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from <insert_4> is <insert_1> (<insert_2>). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host <insert_3> was not running. If this is the case, perform the relevant operations to start the <insert_4> listening program, and try again.

    Most common cause:
    This is a channel connection problem and this happens most frequently when:

    • Listener is not running
    • Incorrect settings in inetd.conf
    • QMGR is not running
    • Routing information in the queue remote's rname or rqmname incorrect
    • Routing information in the channel's conname or xmitq is incorrect


    Diagnostic hints and tips:
    • An FFDC report is generated that will help you diagnose the failure. Use the probe id in the FFDC to search for known problems.
    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination

    Click here for most recent troubleshooting documents


    AMQ9208 Error on receive from host <insert_3>

    Explanation:
    An error occurred receiving data from <insert_3> over <insert_4>. This may be due to a communications failure.

    Response:
    The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

    Most common cause:
    Return codes 10054 (Windows), 73 (AIX), 131 (Solaris), 232 (HP-UX), 104 (Linux), or 3246 (iSeries) means the connection is reset by peer (ECONNRESET). This usually indicates a problem in the TCP/IP network. There are numerous reasons TCP/IP will sent a reset.

    Reasons For TCP/IP Resets

    • An application request a connect to a port and ip address for which no server is Listening
    • An application closes a socket with data still in the application receive buffer. The connection is reset to allow the remote partner to know that the data was not delivered.
    • Any data that arrives for a connection that has been closed can cause a reset.
    • An application closes a socket and sets the linger socket option to zero. This will notify TCP/IP that the connection should not linger.
      • Note: MQ does not code the linger socket option, therefore MQ will not cause a reset.
    • An invalid tcp segment arrives for a connection, for example, a bad acknowledge or sequence number can cause a reset.
    • The connect request times out. TCP gives up trying to connect to an particular port and ip address and resets the connection.
    • A Firewall can reset connections if the packet does not adhere to the firewall rules and policies. For example a source or destination port or ipaddress does not match the firewall rule or policy.
    • The retransmit timer expires. TCP gives up trying to retransmit a packet and resets the connection.
    • A bad hardware device can cause resets

    Diagnostic hints and tips:
    Use TCP/IP packet and a sniffer traces to determine why the reset occurred.

    See instructions to gather TCP/IP packet traces

    Click here for most recent troubleshooting documents


    AMQ9209 Connection to host <insert_3> closed

    Explanation:
    An error occurred receiving data from <insert_3> over <insert_4>. The connection to the remote host has unexpectedly terminated.

    Response:
    Tell the systems administrator.

    Most common cause:
    Incorrect settings in /etc/services and INETD.CONF files.

    Diagnostic hints and tips:

    • Verify that INETD.CONF and /etc/services files match the name of the queue manager and listener port.
    Try using the runmqlsr command on the remote queue manager (receiver side)
    Click here for most recent troubleshooting documents


    AMQ9213 A communications error for <insert_4> occurred

    Explanation:
    An unexpected error occurred in communications.

    Response:
    The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

    Most common cause:
    The inetd configuration file did not have the correct information or syntax.

    Diagnostic hints and tips:
    Try using the runmqlsr command on the remote queue manager (receiver side)
    See runmqlsr (run listener) in the WebSphere MQ Information Center

    Click here for most recent troubleshooting documents


    AMQ9228 The <insert_4> responder program could not be started

    Explanation:
    An attempt was made to start an instance of the responder program, but the program was rejected.

    Response:
    The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the responder program later). The <insert_5> reason code was <insert_1>.

    Most common cause:
    The inetd configuration file did not have the correct information or syntax.

    Diagnostic hints and tips:
    Try using the runmqlsr command on the remote queue manager (receiver side)
    See runmqlsr (run listener) in the WebSphere MQ Information Center


    Click here for most recent troubleshooting documents


    AMQ9503 Channel negotiation failed

    Explanation:
    Channel <insert_3> between this machine and the remote machine could not be established due to a negotiation failure.

    Response:
    Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.

    Most common cause:
    This error can is raised for many reasons

    Diagnostic hints and tips:

    • The queue manager error logs and @System error log may have other message related to the failure that will help you with problem determination.
    • An FFDC report may be generated and it could help you diagnose the failure. Use the probe id in the FFDC to search for known problems.

    Click here for most recent troubleshooting documents


    AMQ9526 Message sequence number error for channel <insert_3>

    Explanation:
    The local and remote queue managers do not agree on the next message sequence number. A message with sequence number <insert_1> has been sent when sequence number <insert_2> was expected.

    Response:
    Determine the cause of the inconsistency. It could be that the synchronization information has become damaged, or has been backed out to a previous version. If the situation cannot be resolved, the sequence number can be manually reset at the sending end of the channel using the RESET CHANNEL
    command.

    Most common cause:

    • Manually resetting a receiver channel message sequence number
    • Deleting and redefining a channel
    • Two instances of the same Receiver channel

    Diagnostic hints and tips:
    • Never reset a Receiver channel's message sequence number.
    • Reset the Sender channel message sequence number to correct this situation.

      See: RESET CHANNEL

    Click here for most recent troubleshooting documents

    Product Alias/Synonym

    WMQ MQ

    Rate this page:

    (0 users)Average rating

    Add comments

    Document information


    More support for:

    WebSphere MQ
    Problem Determination

    Software version:

    5.3, 6.0, 7.0, 7.0.1, 7.1, 7.5

    Operating system(s):

    AIX, HP NonStop, HP-UX, IBM i, Linux, OpenVMS, Solaris, Windows

    Reference #:

    1265188

    Modified date:

    2013-09-05

    Translate my page

    Machine Translation

    Content navigation