| Author |
Message
|
| LazyBoy |
 Posted: Mon May 15, 2006 1:43 am Post subject: Error connecting to workflow Client |
 |
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Hi All,
I am trying to configure client on windows system.
I have copied channel table file from AIX system and pasted in c:\program files\ibm websphere mq workflow\chltabs\ folder.
I have set Path environment variable to MQClient.
When i try to connect to Workflow Client i get this Error:
FMC_API_ERROR_COMMUNICATION:communication Error.
And when i run fmczccd utility on command prompt ,i get the following output:
The channel table in the profile is: C:\program files\ibm websphere mq workflow\chltabs\MQWFCHLTEST.TAB
The connect name found in the profile : FMC.FMCGRP.FMCSYS,FMCQM
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : test(6010)
TCP/IP-addr : test
TCP-Port : 6010
Status : ok
---------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Ping to server gomati was successful.
Unexpected exception occured.FmcFMLException, MQReturnCode=2, MQReasonCode=2058, MQObjectName=FMCQM,Connect_to_QM, severe error
Any one please help me to resolve the problem. |
|
| Back to top |
|
 |
| hos |
| Posted: Mon May 15, 2006 4:09 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
is TCP/IP-addr test a valid MQWF AIX server box?
Or is the hostname of your MQWF AIX box gomati?
Is MQWF started on your AIX box?
Did you create a configuration on your client that matches the settings of your AIX MQWF server?? |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Mon May 15, 2006 4:21 am Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Hi
The name of AIX server is gomati,i edited the output.
Yes, MQWF is started and i have created the same configuration as per the server.
Actually the same configuration is working on another system where MQ client is installed , but its not working on system where Mq server is installed. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon May 15, 2006 7:35 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Do you have MQ Server also on the client box. If yes, how did you do this
| Quote: |
| I have set Path environment variable to MQClient. |
My guess is you haven't set this in the right env.
Set it in the command line, run fmczccd and make sure you connect OK to the server and bring up the client from command line (not from the windows shortcut, but from command line where you have setup the env). |
|
| Back to top |
|
|
| vennela |
| Posted: Mon May 15, 2006 7:37 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| LazyBoy |
| Posted: Sat May 20, 2006 1:34 am Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Hi vennela,
Quote:
I have set Path environment variable to MQClient.
I mean in the Path enviroment variable i have set to "C:\program files\ibm websphere mq workflow\BIN\MQClient"
When i run fmczccd command i get this output.
The channel table in the profile is: C:\program files\ibm websphere mq workflow\chltabs\MQWFCHLTEST.TAB
The connect name found in the profile : FMC.FMCGRP.FMCSYS,FMCQM
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : gomati(5010)
TCP/IP-addr : gomati
TCP-Port : 5010
Status : ok
---------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Ping to server gomati was successful.
Unexpected exception occured.FmcFMLException, MQReturnCode=2, MQReasonCode=2058, MQObjectName=FMCQM,Connect_to_QM, severe error
Any one Please help me resolve this error. |
|
| Back to top |
|
|
| jmac |
| Posted: Sat May 20, 2006 5:56 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Isnt 2058 a QueueManager issue? Is you Qmgr running?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Sun May 21, 2006 8:13 pm Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Yes, the Queue manager is running on server.
As, i said earlier the same configuration is working on another system where MQ Client is installed,but its not working on system where Mq server is installed. |
|
| Back to top |
|
|
| hos |
| Posted: Sun May 21, 2006 10:44 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
When did you change the Path setting? It has to be done
before the configuration is created because the configuration already contains this info and it must match with the Path settings. In other words: you cannot arbitrary switch the Path setting and use any configurationID with any setting.
This message indicates that the queue manager (cluster) is not visible from your client box. I am no the MQ expert to advise how to make it visible but some others in this forum are  |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Sun May 21, 2006 10:46 pm Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
| I set Path variable before creating the configuration. |
|
| Back to top |
|
|
| sarasu |
| Posted: Wed May 24, 2006 6:03 am Post subject: |
|
|
Master
Joined: 02 Feb 2006
Posts: 229
|
Have you made any settings in WAS Admin console? The WebSphere MQ JMS Provider under Resources, there will be Configurations you need to set those configurations set to server1. Afetr that in additional properties you need to make some more settings to "WebSphere MQ queue connection factories" and "WebSphere MQ queue destinations".
Hope this will work |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Wed May 24, 2006 8:10 pm Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
|
| Back to top |
|
|
| chintu |
| Posted: Thu May 25, 2006 9:55 am Post subject: |
|
|
Acolyte
Joined: 27 Dec 2004
Posts: 64
|
| LazyBoy wrote: |
Yes, the Queue manager is running on server.
As, i said earlier the same configuration is working on another system where MQ Client is installed,but its not working on system where Mq server is installed. |
If you have not tried rebooting the system(client),try that. I came across this (or a similar) prob a long while ago.Even though the environment variable points to MQClient, i guess its not actually updated, hence the WF client is looking for QM on the client box. |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Thu May 25, 2006 8:11 pm Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
| Yes,i did restart several times. |
|
| Back to top |
|
|
|
|
