---
title: "IBM MQ - Troubleshooting"
slug: "ibm-mq-troubleshooting"
updated: 2025-01-01T07:47:00Z
published: 2025-01-01T07:47:00Z
canonical: "docs.biztalk360.com/ibm-mq-troubleshooting"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biztalk360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IBM MQ - Troubleshooting

## **Steps to establish client server connection**

- Open MQ Explorer as Administrator in Client machine.
- Right click on Queue Manager and click "Add Remote Queue Manager".
- Enter the Queue Manager present in server machine that you are trying to connect. Choose "Connect directly".
- Enter the Host name or IP address of the server machine and the respective Queue Manager's Channel Port Number
- Click "Next" twice and Check "Enable user identification" and Provide the BizTalk360 User Account.
- Click "Next" until last screen and enter the provided user account password when prompted.

## **Errors while connecting from BizTalk360 to IBM MQ**

User might face errors or technical challenges while configuring BizTalk360 to monitor IBM MQ queues. Some of the common error codes are:

- MQRC_UNKNOWN_OBJECT_NAME - Reason: Queue name is wrong or Specified Queue not available in the Queue Manager.
- 2538 – MQRC_HOST_NOT_AVAILABLE / AMQ4059
- 2035 – MQRC_NOT_AUTHORIZED / AMQ4036
- 2059 – MQRC_Q_MGR_NOT_AVAILABLE

**We can see the details about the errors and resolution:**

Names are **case sensitive** in MQ, hence always check the provided values in BizTalk360 is same as in MQ Explorer

## **MQRC_HOST_NOT_AVAILABLE – 2538 / AMQ4059**

Connect to a queue manager but the attempt to allocate a conversation to the remote system failed.

![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1722427561177.png)

**Reason:**

1. The connection name in the client channel definition is incorrect
2. The listener has not been started on the remote system
3. The network is currently unavailable
4. A firewall blocking the port, or protocol-specific traffic
5. The security call initializing the IBM MQ client is blocked by a security exit on the SVRCONN channel at the server

**Resolution:**

1. Make sure all the connection details provided (Queue Manager name, Host name, Port, User Account and Password) is correct.
2. Right on Queue Manager and click "Remote Administration". Ensure that SYSTEM.ADMIN.SVRCONN channel and Listener.TCP listener are available (If not available create new one) and the listener status is "Running" else Start the listener![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1722427959149.png)
3. In the client machine, run the following command in PowerShell to check the check network connectivity:PowerShellPowerShell

```powershell
Test-NetConnection -ComputerName serverHostname -Port portNumber -InformationLevel Detailed
```

## **MQRC_NOT_AUTHORIZED – 2035 / AMQ4036**

**![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1722428022857.png)**

#### 

**Reason:**

1. The user account trying to access the Queue Manager is blocked by Channel Authentication Records

**Resolution****:**

Either delete the "Block" rule that contains the User List as "*MQADMIN" or Modify/Add rule that allows the user account.

Please refer to this document for instructions on overriding the default rule for an MQ-admin user: [IBM MQ - Permissions](/docs/ibm-mq-permissions#mqadmin-override-default-rule)

## **MQRC_Q_MGR_NOT_AVAILABLE – 2059**

**Reason:**

1. The default queue manager is not running
2. The MQ listener program associated with the default queue manager is not running
3. The default queue manager is not defined on the local system

**Resolution:**

1. Determine the name of the queue manager
2. Verify that the queue manager exists on the local machine, and that it is running
3. Verify that the listener program is running
4. Verify that queue manager trying to connect is the default queue manager
5. If necessary, make queue manager as the default queue manager