Why am I getting "MQRC_UNKNOWN_CHANNEL_NAME" error when I try to add IBM MQ monitor ?
This error occurs when the channel name provided while adding the monitor is wrong or the user doesn't have permission to access the channel.
- Make sure you have provided the channel name in exact case.
- Make sure that the user you have provided has the permission to access the channel.
Refer the following IBM documentation for more details :
If the issue still exists, reach out to our support with the screenshot of the error obtained to appmanager-support@manageengine.com along with the latest Support Information File (SIF) from Applications Manager with print all logs enabled for analysis.
New to ADSelfService Plus?
Related Articles
I'm getting "MQRC_NOT_AUTHORIZED" error in IBM WebSphere MQ. What could be the reason ?
The reason could be any one of the following : Authentication is enabled in the MQ Queue Manager, but the user details are not provided in the add monitor page of WebSphere MQ monitor. The user provided is not authorised to connect to MQ. Password ...I'm getting "mqrc_host_not_available" error in IBM MQ monitoring. What could be the reason ?
The reasons could be any of the following : The listener has not been started on the remote system. The connection name in the client channel definition is incorrect. The network is currently unavailable. A firewall blocking the port, or ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Prerequisites for adding IBM MQ monitor via SSL
To add the IBM monitor via SSL, please follow the required steps given below with respect to authentication type: SSL Authentication is optional (One-way SSL) If SSL Authentication is optional (One-way SSL), you need to load the MQ server's CA ...DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...