| Author |
Message
|
| johndriscoll |
 Posted: Thu Sep 09, 2004 8:01 am Post subject: Need Some Help.... |
 |
|
Newbie
Joined: 09 Sep 2004
Posts: 3
|
I need some help. We are getting a TCP/IP error in our Event viewer posted by MQSERIES.... The error is as follows
Event Type: Error
Event Source: MQSeries
Event Category: None
Event ID: 9202
Date: 9/9/2004
Time: 9:06:39 AM
User: N/A
Computer: C0100437
Description:
Remote host 'BATCH_2.EH.PWEH.COM (10.30.244.16) (1414)' not available, retry later.
The attempt to allocate a conversation using TCP/IP to host 'BATCH_2.EH.PWEH.COM (10.30.244.16) (1414)' 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 10055 (X'2747'). 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 'BATCH_2.EH.PWEH.COM (10.30.244.16) (1414)' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again.
Can anyone help point me where to look for what resource it is lacking or to fix..
Thanks in advance
Peter J Knight  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Sep 09, 2004 8:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The error message suggests you check the listener on the remote machine.
Also, you can try using ping from the local server to see if you can even reach the remote machine at all.
Then you can try using telnet to connect to the listener port, to see if you get a response.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| johndriscoll |
| Posted: Thu Sep 09, 2004 8:24 am Post subject: |
|
|
Newbie
Joined: 09 Sep 2004
Posts: 3
|
Thanks ...
The Listener seems to be fine...... does the 10055 message indicate that
the problem is on the Win 2000 client computer or the Unix machine where the MQ series queue manager resides???
If its the remote node, is there a TCP paramter that needs to be tweaked
(either on the win 2000 client or the Unix Box where the MQ queue manager is)
Once again thats for any input...
Peter : Knight |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Sep 09, 2004 8:43 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 09, 2004 9:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Again, can you ping the Unix machine from the windows machine?
Can you telnet to the listener port on the Unix machine from the Windows machine?
The windows hotfix mentioned in Ron's posting should not be applicable to Windows 2000.
Can you run amqsgetc or amqsputc from the windows machine?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Sep 09, 2004 9:46 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Yes, he should definitely be beyond the hotfix. However, the thing that I found interesting was that the 10055 looks more like a Windows error than a WMQ error. |
|
| Back to top |
|
|
|
|
