| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error AMQ4203 reason MQCONN error 2059 |
« View previous topic :: View next topic » |
| Author |
Message
|
| AvatarSingh |
 Posted: Tue Nov 06, 2001 5:55 pm Post subject: |
 |
|
Newbie
Joined: 05 Nov 2001
Posts: 1
|
My environemnt : MQSeries server being installed on Win2K sp2 adn domain server on WinNT 4.0 sp6.
While default configuration I get the error "Unable to setup default configuration error AMQ4203' with detail as 'Function MQCONN failed with reason 2059'
Can anybody help with a resolve. I checked MUSR_MQADMIN user_id configured as Log on as a batch job in DCOMCNFG. But this user is shown as part of the WIn2K machine and not the domain thsi server is attached to. This maybe a reason which I am going to explore. Other than that if anybody has a solution please oblige.
Avatar
|
|
| Back to top |
|
 |
| msiegert |
| Posted: Wed Nov 07, 2001 12:03 am Post subject: |
|
|
Apprentice
Joined: 05 Aug 2001
Posts: 29
|
Hi!
Do you already have set up a QMGR?
RC 2059 normally has nothing to do with authorization problems. 2059 means:
MQRC_Q_MGR_NOT_AVAILABLE
Queue manager not available for connection.
On an MQCONN or MQCONNX call, the queue manager identified by the QMgrName parameter is not available for connection at this time.
On OS/390, for CICS applications, this reason can occur on any call if the original connect specified a queue manager whose name was recognized, but which is not available.
On OS/400, this reason can also be returned by the MQOPEN and MQPUT1 calls, when MQHC_DEF_HCONN is specified for the Hconn parameter.
If the connection is from an MQ client application, this reason code can occur if there is an error with the client-connection or the corresponding server-connection channel definitions.
On OS/390, this reason code can also occur if the optional MVS/ESA client attachment feature has not been installed.
This reason also occurs if an application attempts to connect to a queue manager within a group (see the QMgrName parameter of MQCONN), when none of the queue managers in the group is available for connection at this time.
Corrective action: Ensure that the queue manager has been started. If the connection is from a client application, check the channel definitions.
This might help
Marc
|
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 07, 2001 10:39 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| When we've seen this problem in the past, the most common cause has been that there is some kind of monitoring software running. Do you have some kind of third party package that monitors your system (virus checker)? The other cause (although infrequent) has been the need to disable terminal services. Hope this helps. |
|
| 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
|
|
|
|
