| Author |
Message
|
| kayoumt |
 Posted: Thu Sep 20, 2007 12:34 am Post subject: AMQ9503: Channel negotiation failed - Reason Code 2059 |
 |
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
Need help again.
I reformated my PC server, did a very simple and clean LINUX RHEL4 and very simple and clean MQ Server installation on it. On my XP machine I tried to run C++ MQ applications (connecting them remote to the LINUX box MQ server). The queue manager connection failed with Reason Code 2059.
I verified anything and found nothing suspect :
- MQ Explorer is running on my XP machine and is capable to connect to the LINUX queue manager and to show queue manager informations.
- 1414 port on LINUX is enabled for TCP and UDP.
- I compiled my c++ applications with imqb23vn.lib and imqc23vn.lib to enable client mode compilation.
???
Any help will be appreciated.
There's no FDC generated, but error messages has been printed in the log (see below) :
-------------------------------------------------------------------------------
09/20/2007 02:27:32 AM - Process(4446.4) User(mqm) Program(amqrmppa)
AMQ9503: Channel negotiation failed.
EXPLANATION:
Channel 'CADS6.CLI1.SVRCONN' between this machine and the remote machine could
not be established due to a negotiation failure.
ACTION:
Tell the systems administrator, who should attempt to identify the cause of the
channel failure using problem determination techniques. For example, look for
FFST files, and examine the error logs on the local and remote systems where
there may be messages explaining the cause of failure. More information may be
obtained by repeating the operation with tracing enabled.
----- amqrmsaa.c : 605 --------------------------------------------------------
09/20/2007 02:27:32 AM - Process(4446.4) User(mqm) Program(amqrmppa)
AMQ9492: The TCP/IP responder program encountered an error.
EXPLANATION:
The responder program was started but detected an error.
ACTION:
Look at previous error messages in the error files to determine the error
encountered by the responder program.
----- amqrmrsa.c : 459 -------------------------------------------------------- |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Sep 20, 2007 12:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Do a search for 2059 in the forum - if it's not the most common error out of MQ it's certainly top 5. You'll find a wealth of discussions around what other people have tripped over.
If it was me, I'd start by seeing if the supplied amqsputc code could connect. This would focus the problem on either your code or a network / configuration issue (which would be my bet).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Sep 20, 2007 12:53 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Quote: |
| examine the error logs on the ... remote systems |
Have you done this?
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| kayoumt |
| Posted: Thu Sep 20, 2007 1:08 am Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
MQSERVER=CADS6.CLI1.SVRCONN/TCP/192.168.2.100(1414)
C:\wmqclient\Windows\MSI\Tools\c\Samples\Bin>amqsputc TESTQUEUE QM_CADS6
Sample AMQSPUT0 start
MQCONN ended with reason code 2059 |
|
| Back to top |
|
|
| kayoumt |
| Posted: Thu Sep 20, 2007 1:10 am Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
Nigelg,
Yes, I checked log file. The only thing I found is AMQ9503 and AMQ9492 errors. I sent them in my first post. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 20, 2007 1:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kayoumt wrote: |
MQSERVER=CADS6.CLI1.SVRCONN/TCP/192.168.2.100(1414)
C:\wmqclient\Windows\MSI\Tools\c\Samples\Bin>amqsputc TESTQUEUE QM_CADS6
Sample AMQSPUT0 start
MQCONN ended with reason code 2059 |
You've got a configuration error of some kind. If Explorer is working (as you indicated in your post), compare the settings of SYSTEM.ADMIN.SVRCONN with CADS6.CLI1.SVRCONN as a next step.
Then work through the problem until it's resolved! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kayoumt |
| Posted: Thu Sep 20, 2007 2:02 am Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
I solved my problem.
I found out that there was a CCSID problem. In fact, I quickly discovered a couple of little bit mysterious things.
1) When my client connected to a XP queue manager, variable MQCCSID value was 65001 (windows UTF8 code). It seems that if the queue manager server changes to LINUX MQCCSID value must change to 1208 ???
2) My C++ code does not like channel setting by MQSERVER. It seems it cannot handle the variable and does not want to have it set if channel is hard-coded in code ???
3) How MQ Explorer did for working with bad CCSID setting and mycode and amqsputc ended with 2059 error ?
4) I never knew that MQ generate log error files on client side also. I found my CCSID error in C:\Program Files\IBM\WebSphere MQ\errors if there is solely a client installed on machine.
Thanks for any answer to these non urgent questions. |
|
| Back to top |
|
|
|
|
