| Author |
Message
|
| anpati1 |
 Posted: Wed Oct 03, 2007 5:57 am Post subject: Urgent...please help MBToolkit domain for Queue manager |
 |
|
Novice
Joined: 07 Jun 2007
Posts: 24
Location: Marlow, UK
|
Hi,
I am unable to create a domain connection in MBtoolkit to my Queue Manager. My listener is running and also the Configmanager is started. Please can you help urgently ...
| Code: |
Could not connect to queue manager 'BRK_QMGR' (MQ reason code 2195)
|
Please could you advise what trace methodology I need to adopt? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 03, 2007 6:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Look at the FDC file associated with the 2195 reason code.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anpati1 |
| Posted: Wed Oct 03, 2007 6:37 am Post subject: |
|
|
Novice
Joined: 07 Jun 2007
Posts: 24
Location: Marlow, UK
|
This is from the queue managers error log. Does it help anyway to pinpoint the problem? Will applying fixpack solve the problem? Never used FDC... unable to find one aswell.. Please help!
| Code: |
User(MUSR_MQADMIN) Program(amqrmppa.exe)
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record
these values and tell the systems administrator.
|
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 03, 2007 6:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There should be a file in the errors directory, either for the whole MQ install or for the qmgr, that ends with .FDC.
It should hopefully exist and give you more information (although a lot of it will be meaningless to anyone other than support... focus on the header block) about why things failed.
You can also search here for that TCP/IP return code.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rajmq |
| Posted: Wed Oct 03, 2007 7:15 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
What is version of wmq/wmb mgr using ?
_________________
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified System Administrator - WebSphere Business Integration Message Broker V6.0 |
|
| Back to top |
|
|
| anpati1 |
| Posted: Wed Oct 03, 2007 7:16 am Post subject: |
|
|
Novice
Joined: 07 Jun 2007
Posts: 24
Location: Marlow, UK
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 03, 2007 7:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I really hope not.
Nobody should be upgrading v5.2 to v5.3. Especially with WMBT v6.
MQ V6 please.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| anpati1 |
| Posted: Wed Oct 03, 2007 7:50 am Post subject: |
|
|
Novice
Joined: 07 Jun 2007
Posts: 24
Location: Marlow, UK
|
Apologies for not being specific on the solution. I have V6 except that the issue was with my windows TCP socket. I followed the instructions as per Microsoft article
[url]
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b318584
[/url]
and The listener is accepting connections.
Again, the issue was with TCP sockets and not mq version. |
|
| Back to top |
|
|
| anpati1 |
| Posted: Wed Nov 07, 2007 7:23 am Post subject: |
|
|
Novice
Joined: 07 Jun 2007
Posts: 24
Location: Marlow, UK
|
I have summarised the steps to resolve the
| Code: |
A communications error for TCP/IP occurred.
An unexpected error occurred in communications.
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record these values and tell the systems administrator. |
problem on windows machine as below.
1. Identify if there is an Layered Service Provider. The diagnosis can be done using the programs>Accessories>System Tools>System Information>
SystemSummary-Components-Network-Protocol
if there is a LSP it will appear something as BMI over [MSAFD Tcpip [TCP/IP]] instead of MSAFD Tcpip [TCP/IP].
2. Identify the program that constitutes the LSP and uninstall it.(I had vodafone mobile connect which installed the ByteMobile inc. LSP.)
3. Shutdown and start the pc and repeat step 1 to confirm the default value MSAFD Tcpip [TCP/IP] is available.
4. Run the guidedhelp tool from microsoft to confirm there is no other corruption to winsock2 and if necessary reinstall tcp/ip.
http://support.microsoft.com/kb/811259
Cheers,
Anand |
|
| Back to top |
|
|
|
|
