| Author |
Message
|
| mangoMan |
 Posted: Mon Oct 23, 2006 3:52 pm Post subject: Mesg Broker Toolkit is unable to communicate with ConfigMgr |
 |
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
I'm trying to install Message Broker V6 on WinXP. I've successfully executed mqsicreateconfigmgr. I have queue manager listening on port 1415. The broker is installed on the C:\ drive and the toolkit is installed on the D:\ drive. I'm trying to create a new Domain in Broker Admin perspective of Toolkit. Getting error "BIP0914E Message Brokers Toolkit is unable to communicate with the Configuration Manager". I've checked that the Qmgr is running and the listener is up. I don't see any errors in the event log.
Any help would be appreciated.
Thanks. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Oct 23, 2006 4:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What shows up in the "details" section of the error message?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Oct 24, 2006 7:44 am Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Here is the message from the details section:
| Quote: |
| Either the network is down, the queue manager 'WBRK_CONFIG_QM' is not running, or there is no related listener running on port 1417 (MQ reason code 2059 while trying to connect) |
I get the same 2059 error when I try to connect to the configuration manager through the CMP API exerciser. But the qmanager and the listener are up and I am able to connect to it and put a message on a test queue through the amqsput sample application.
I did put the CMP jar file in my windows CLASSPATH.
Also, when I use the amqsputc application with I get 2059 as well and I see this error message in the event log. I used the following in the mqserver variable:
MQSERVER=SYSTEM.DEF.SVRCONN/TCP/10.199.169.146(1417)
Also tried localhost.
Remote host 'IBM-X6A2G3VPRSX (ÌU¥qäU¥q) (1417)' not available, retry later.
| Quote: |
The attempt to allocate a conversation using TCP/IP to host 'IBM-X6A2G3VPRSX (ÌU¥qäU¥q) (1417)' was not successful. However the error may be a transitory one and it may be possible to successfully allocate a TCP/IP conversation later.
Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from TCP/IP is 10061 (X'274D'). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host 'IBM-X6A2G3VPRSX (ÌU¥qäU¥q) (1417)' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again. |
[/quote] |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 24, 2006 9:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What are the typical causes of MQRC 2059?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Oct 24, 2006 11:08 am Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Could it be a listener or a server con channel problem? Can't figure out the problem. They are both running. Well the Servercon is not running but should get triggered. Shouldn't it?
Here is the description from the info center:
On an MQCONN or MQCONNX call from an MQ client application:
* Attempting to connect to a queue manager within an MQ-client queue-manager group when none of the queue managers in the group is available for connection (see the QMgrName parameter of the MQCONN call).
* If there is an error with the client-connection or the corresponding server-connection channel definitions.
* On z/OS, if the optional OS/390 client attachment feature has not been installed. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 24, 2006 11:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you use telnet to connect to the listener port?
Did you open the listener port in whatever firewall you have?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Oct 24, 2006 12:13 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Yes, I can connect to 1417.
I have disabled the firewall. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 24, 2006 12:40 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So you can telnet to the port, but you can't use amqscnxc or amqsputc to connect?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Oct 24, 2006 1:21 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Yes, that is correct.
Very very strange. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Oct 24, 2006 1:43 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
In one of the posts you mentioned 1415 and others you are referring to 1417
Also, the IP looks like VPN Virtual Adapter IP. If it is a stand alone, setup, try to use localhost or something similar. I am not sure if this would resolve it though |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Oct 24, 2006 2:23 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
I have tried it all:
SYSTEM.DEF.SVRCONN/TCP/ComputerName.CORP.COM(1417)
SYSTEM.DEF.SVRCONN/TCP/domain_ipaddress(1417)
SYSTEM.DEF.SVRCONN/TCP/ipaddress(1417)
SYSTEM.DEF.SVRCONN/TCP/localhost(1417) |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Oct 24, 2006 3:05 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Windows XP.
MQSeries is running under the Local System Account |
|
| Back to top |
|
|
| mangoMan |
| Posted: Wed Oct 25, 2006 2:45 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
| But they just added my computer to the corporate domain. Could that have something to do with the client not connecting? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 25, 2006 3:08 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The client would get a 2035 if it had to do with IDs and "the corporate domain".
A 2059 is a communications problem, not an authorizations problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Wed Oct 25, 2006 4:32 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Ok.
Does anyone know why I am getting these unreadable characters in the error message in the application event log
Remote host 'localhost (ÌU¥qäU¥q) (1417)' not available, retry later.
What is (ÌU¥qäU¥q) ???? |
|
| Back to top |
|
|
|
|
