Command Server Queue Is Open Try Again Later

Resolving The Problem

This document contains a listing of common MQ mistake messages and explains the virtually likely reason for the mistake. There tin be many reasons for each of these letters, however this is our attempt to aid you sympathise the virtually likely crusade, and lead you to the near recent troubleshooting documents for a quick solution.

Click on the error bulletin 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'south 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 automobile and the user is attempting to connect to a remote queue manager, and then it tin can remotely administer MQ objects. The endeavour is failing because the initiator user ID does not have the say-so to admission one or more than objects on the remote organization.

Most common cause:
The Windows user ID:

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

Diagnostic hints and tips:
The easiest mode to resolve this problem is to make the Windows user ID a super user on the local and remote systems. The user should take full authority and access to all MQ objects on the remote organisation. Brand this user a fellow member of the "mqm" group in the Os environments that take an "mqm" group divers.

Additional information:
Ensure that yous 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 tin exist the WebSphere MQ listener, or the inetd daemon in as appropriate.
4. The server-connexion channel, chosen Organisation.ADMIN.SVRCONN, exists on every remote queue manager. This channel is mandatory for every remote queue managing director being administered. Without it, remote assistants is not possible. You can create the aqueduct 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.Respond.MODEL. Y'all tin can create the queue using the following MQSC command: Ascertain QMODEL(SYSTEM.MQEXPLORER.Reply.MODEL)

Click here for near recent troubleshooting documents

AMQ4100 The MMC document file <filename> could non exist 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 non.

User Response:
Cheque that the disk is non 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 accept permission to admission a Registry Entry
• MUSR_MQADMIN user ID password was changed

Diagnostic hints and tips:

• Run the post-obit commands to reregister the MQ Service and the proxy:

amqmsrvn -regserver
regsvr32 amqmspsn.dll
• Add the MUSR_MQADMIN to the administrators group

Click hither for most recent troubleshooting documents

AMQ4128 Could not kickoff the iKeyMan program.

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

Click hither for most recent troubleshooting documents

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

Explanation:
Ane 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 terminate any Performance Monitor tasks. If the procedure locking WebSphere MQ files cannot be identified, installation tin usually proceed following a reboot, with the WebSphere MQ service disabled.

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

Diagnostic hints and tips:
Yous tin prepare an installation parm that will allow the installation to consummate, even if MQ DLL's are being used. For details see APAR IC57153.

Click here for nigh recent troubleshooting documents

AMQ6090 WebSphere MQ was unable to brandish an fault message <insert_6>

Explanation:
MQ has attempted to display the bulletin associated with return code hexadecimal <insert_6>. The return code indicates that there is no bulletin 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 centre. Do not discard these files until the problem has been resolved.

Most mutual cause:

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

Diagnostic hints and tips:

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

Click hither for virtually 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:
Apply the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM back up center. Exercise not discard these files until the problem has been resolved.

Most mutual crusade:
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 y'all diagnose the failure. Use the probe id in the FFDC to search for known bug.
• The queue manager error logs and @System error log may have other message related to the failure that will help you lot with problem conclusion.

Click here for near recent troubleshooting documents

AMQ6125 An internal WebSphere MQ mistake has occurred

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

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

Most common cause:
This error tin is raised for many reasons, information technology is a very generic error message.

Diagnostic hints and tips:

• An FFDC report is generated that volition assist you diagnose the failure. Utilize the probe id in the FFDC to search for known problems.
• The queue manager error logs and @Arrangement fault log may take other bulletin 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 keep to wait for access. If the situation does not resolve itself and y'all suspect that your system is locked and so investigate the process which owns the semaphore. The PID of this process will be documented in the accompanying FFST.

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

Diagnostic hints and tips:

• Ensure that all applications disconnect from MQSeries before catastrophe.
• An FFDC report is generated that will aid you diagnose the failure. Employ the probe id in the FFDC to search for known problems.
• The queue manager mistake logs and @System error log may have other message related to the failure that volition assist y'all 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 mistake recording routine has been called. The declining process is process <insert_1>.

Response:
Employ the standard facilities supplied with your organization to record the problem identifier, and to salvage the generated output files. Contact your IBM support center. Exercise not discard these files until the problem has been resolved.

About common cause:
This information technology is a very generic fault that informs you that another process has failed. Utilise the process number in the bulletin insert to correlate it with the FFDC record for the failing process.

Diagnostic hints and tips:

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

Click hither for about recent troubleshooting documents

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

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

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

Near mutual 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. Employ 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 lot with problem determination

Click here for most recent troubleshooting documents

AMQ7469 Transactions rolled back to release log infinite

Explanation:
The log infinite for the queue manager is becoming total. One or more long-running transactions have been rolled back to release log space and then that the queue director can keep to procedure requests.

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

Well-nigh 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 organization running and will require a queue director 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. Increment the value of the LogPrimaryFiles & LogSecondaryFiles. The sum of both accept to be less than or equal to 63 (V5.iii) 511(V6.0)
2. Finish 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 hither 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 managing director 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 bachelor in the log. If the reason lawmaking value indicates that the error was associated with a particular parameter, the parameter concerned is <insert_4>.

Response:
Correct the error and and so try the control once again.

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

Diagnostic hints and tips:

• An FFDC report is generated that will aid yous diagnose the failure. Use the probe id in the FFDC to search for known problems.
• The queue managing director error logs and @System error log may have other bulletin related to the failure that will assistance y'all with problem determination

Click here for virtually recent troubleshooting documents

AMQ9202 Remote host <insert_3> non available, retry after

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

Response:
Attempt the connectedness again later. If the failure persists, tape the mistake values and contact your systems administrator. The return lawmaking from <insert_4> is <insert_1> (<insert_2>). The reason for the failure may be that this host cannot reach the destination host. Information technology may also be possible that the listening plan at host <insert_3> was not running. If this is the instance, perform the relevant operations to start the <insert_4> listening program, and try once more.

About 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 non 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 written report is generated that will assistance yous diagnose the failure. Employ the probe id in the FFDC to search for known problems.
• The queue manager error logs and @System fault log may have other bulletin related to the failure that volition help you with problem conclusion

Click here for well-nigh contempo troubleshooting documents

AMQ9208 Error on receive from host <insert_3>

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

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

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

Reasons For TCP/IP Resets

• An application asking 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 let the remote partner to know that the data was not delivered.
• Any data that arrives for a connection that has been airtight tin can cause a reset.
• An awarding closes a socket and sets the linger socket pick to zero. This will notify TCP/IP that the connection should not linger.
• Note: MQ does not code the linger socket choice, therefore MQ will not cause a reset.
• An invalid tcp segment arrives for a connection, for case, a bad acknowledge or sequence number tin can cause a reset.
• The connect request times out. TCP gives upward trying to connect to an particular port and ip address and resets the connexion.
• A Firewall tin reset connections if the parcel does not adhere to the firewall rules and policies. For example a source or destination port or ipaddress does not match the firewall dominion or policy.
• The retransmit timer expires. TCP gives upward trying to retransmit a parcel and resets the connection.
• A bad hardware device tin cause resets

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

Run across instructions to gather TCP/IP parcel 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 connectedness to the remote host has unexpectedly terminated.

Response:
Tell the systems ambassador.

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

Diagnostic hints and tips:

• Verify that INETD.CONF and /etc/services files friction match the proper name of the queue managing director and listener port.

Effort using the runmqlsr control on the remote queue manager (receiver side)

See runmqlsr (run listener) in the WebSphere MQ Information Center

Click here for most recent troubleshooting documents

AMQ9213 A communications mistake for <insert_4> occurred

Explanation:
An unexpected mistake occurred in communications.

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

Most common cause:
The inetd configuration file did not accept the right data or syntax.

Diagnostic hints and tips:
Attempt using the runmqlsr command on the remote queue manager (receiver side)
Come across runmqlsr (run listener) in the WebSphere MQ Data Center

Click here for near recent troubleshooting documents

AMQ9228 The <insert_4> responder programme could not be started

Caption:
An endeavour was made to first an instance of the responder plan, but the plan was rejected.

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

Virtually common cause:
The inetd configuration file did non have the correct data or syntax.

Diagnostic hints and tips:
Try using the runmqlsr command on the remote queue manager (receiver side)
Run into runmqlsr (run listener) in the WebSphere MQ Data Middle

Click here for virtually recent troubleshooting documents

AMQ9503 Channel negotiation failed

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

Response:
Tell the systems administrator, who should attempt to place the cause of the aqueduct failure using problem determination techniques. For example, wait for FFST files, and examine the error logs on the local and remote systems where there may exist letters explaining the cause of failure. More information may exist obtained past repeating the performance with tracing enabled.

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

Diagnostic hints and tips:

• The queue director error logs and @System fault log may have other message related to the failure that volition help you lot with problem determination.
• An FFDC report may exist generated and it could help you diagnose the failure. Use the probe id in the FFDC to search for known bug.

Click here for nearly recent troubleshooting documents

AMQ9526 Message sequence number mistake for channel <insert_3>

Explanation:
The local and remote queue managers practise 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 state of affairs cannot be resolved, the sequence number can be manually reset at the sending end of the channel using the RESET CHANNEL
control.

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 aqueduct's message sequence number.
• Reset the Sender channel message sequence number to correct this situation.

Meet: RESET CHANNEL

Click here for near contempo troubleshooting documents

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Concern Unit of measurement":{"code":"BU053","label":"Deject & Data Platform"},"Component":"Problem Determination","Platform":[{"lawmaking":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","characterization":"Linux"},{"lawmaking":"PF021","label":"OpenVMS"},{"lawmaking":"PF027","characterization":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.0;7.5;vii.1;vii.0.1;7.0;6.0;v.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

phelpsforgaziesing.blogspot.com

Source: https://www.ibm.com/support/pages/common-websphere-mq-messages-and-most-likely-causes

Share this post