| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2067 Error on the Connect in VB. MQAX200 issue? |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Mon Apr 15, 2002 6:47 am Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
We have a VB MQClient app (5.2.1) that has been running well on people PCs. It connects to a remote MQ Server (our MQ Concentrator).We migrated the app to a WIN2000 server (No MQ Queue Manager on this server, just the Client (5.2.1)), where it attempts to connect to that same remote MQ Concentrator. However, we always get...
32000: MQAX200.MQQeueuManager::GetName Completion Code = 2, Reason Code 2067, ReasonName = MQRC_SELECTOR_ERROR
It looks to me that MQ under the covers is doing some sort of MQINQ call during the connect so it can return the QM name, but for some reason is failing in this environment.
While we are getting this error on the app that is running on the WIN2000 server, the WIN2000 pc apps still work OK, which leads me to believe something isn't right on that server. The MQClient install went OK. Any ideas?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Apr 15, 2002 8:50 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
Some more info. We only get this error when running the program under COM+, either on the server or on a desktop pc. When running on a pc under COM+ in a debugger, the error still shows up on the connect, but if we choose to ignore it we can complete the entire transaction with no further MQ errors.
I wonder why COM+ causes the 2067 on the connect?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| muralidhar |
| Posted: Tue Apr 16, 2002 8:30 am Post subject: |
|
|
Acolyte
Joined: 28 Feb 2002
Posts: 50
|
| I experienced same problem. When you use ActiveX control, you need to give inq permission to the userid on both QManager and Queue. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Apr 17, 2002 10:28 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
This app comes in as a client thru a svrcon channel whose MCA USER IDENTIFIER is set to an ID that has unlimited access for all objects. Also, if the app connects outside of COM+, it works clean; inside of COM+, with no other changes, it bombs. Can you think of any other causes?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
