QJE001: Completion Code '2', Reason '2495' - ibm-mq

Using WebSphere MQ version 7.0.1.6 on Platform: WebSphere MQ for AIX Mode: 64-bit O/S: AIX 6.1.
I try to connect from a simple OS project running on Weblogic 11.g to connect to MQ in "Binding" mode type. I get the following:
Error occured when connecting to MQ: Exception occured while unregistering resource; QJE001: Completion Code '2', Reason '2495'
Steps I found on the ibm site
are applied without any result.
Please suggest a solution.

Thanks guys for your comments.
Issue is solved, this link has been helpful:
http://www-01.ibm.com/support/docview.wss?uid=swg21413508

Related

IBM MQ installation Version 8

In one of the windows system the administrator has installed the IBM MQ version 8. But after installation we are not ale to see the IBM MQ (installation 1) listed in the services. and also not able to see the file amqsvc.exe file.
If we launch Prepare Websphere MQ wizard it also just exits without any actions.
But on the control panel -programs and features able to see the IBM MQ installation1 is present . how to find out if the installation was done correctly?
Was this a MQ client installation instead of MQ server installation? how to find out what is the issue here as the MQ service is not present or its related files?

BizTalk and MQ fail when on the same server

I have BizTalk running on a virtual box, that hits my server. It can post messages to the MQ queues without any problem. The issue is when I run BizTalk, which is installed on the same server as MQ, the MQSAgent throws this error:
The adapter has encountered an 'Access Denied' error while attempting to contact the COM+ object on the MQSeries server. Ensure the BizTalk account is added to the Role on the MQSAgent COM+ application*
The virtual box, uses the same MQSAgent as the server. Just to be sure I checked to make sure everything is set up, ie User is added to the COM group and has the role of creater/owner.
I haven't found anything on line where a developer is having the same issue.
Anyone got any ideas?
I never faced this issue but it seems to be a known issue by Microsoft. please check the following Known Issues with the MQSeries Adapter (learn.microsoft.com)

Failed to connect to Websphere MQ Manager

Whenever I connect to a Queue Manager on my Websphere MQ, I get the following error:
An unexpected error(2495) has occurred. (AMQ4999)
The details of this error message says:
An unexpected error (insert_0) has occurred.
I have no idea what this means as I'm new to this. I tried to restart my Websphere MQ as well as the IBM MQSeries server but this still persists. I even tried to create a difference MQ Manager but it still persists. Do you have any idea as to what causes this issue?

How to resolve IBM websphere AMQ4574 error

How to resolve error-'IBM WebSphere Explorer is already running(AMQ4574)'?
I am getting this error while accessing IBM explorer through ssh.
The issue is you cant have more than one explorer running under the same userid anymore...
Read the following for the explanation and potential workaround
http://www-01.ibm.com/support/docview.wss?uid=swg21672390

Websphere MQ error on V7 Queue manager

We upgraded MQ to V7 from V6. after the we are facing this error on executing mq commands.
retrieving local queue manager
Could not load program dspmq:
Dependent module /usr/lib/libmqmcs_r.a(shr.o) could not be loaded.
The module has an invalid magic number.
Referring to IBM site,
http://www-01.ibm.com/support/docview.wss?uid=swg21233269
By no where i specify LIBPATH to /usr/mqm/lib in my AIX machine. But on setting the LIBPATH to "" this issue is resolved.
Could you help me to understand how LIBPATH is set for using MQ Libraries ? Will it be set during installation?
You have not mentioned what release of MQ v7 you migrated to. MQ v7.1 installation does not create any symbolic links under /usr directory. This is because from v7.1, MQ started supporting multi version installations. One has to use SETMQENV command setup MQ environment.
Please follow this link.
Edit: My suspicion is that LIBPATH might have been pointing to some incorrect mq libraries.

Resources