| Author |
Message
|
| olan022 |
 Posted: Thu May 30, 2002 12:31 pm Post subject: FMC_API_ERROR_COMMUNICATION: Communication Error |
 |
|
Acolyte
Joined: 17 Apr 2002
Posts: 50
|
If I am running the Win2000 FMC Workflow Client (runtime) and when I log in to an AIX WF Server I get a
FMC_API_ERROR_COMMUNICATION: Communication Error
dialog box that only has an OK button.
I can log in as this user from MY OWN workstation just fine. From this workstation the error appears. I can log in as myself on this workstation and I get the error too. The workstation with the problem can talk on the network in a regular fashion. I haven't found any references to the FMC_API_ERROR_COMMUNICATION message so don't know exactly how to approach this.
Does anyone have any ideas on this? Thanks. |
|
| Back to top |
|
 |
| vedbhat |
| Posted: Thu May 30, 2002 5:52 pm Post subject: |
|
|
Disciple
Joined: 19 Mar 2002
Posts: 186
Location: Singapore
|
|
| Back to top |
|
|
| kriersd |
| Posted: Mon Jul 22, 2002 6:19 pm Post subject: Check the CCSID |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Look in the event viewer and make sure you don't see any errors for "MQSERIES". It could be that you don't have the correct code table on that machine.
437 <-- code table for NT systems
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| Hari |
| Posted: Fri Nov 29, 2002 3:07 am Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Hi,
I am getting a similar problem....
FMC_API_ERROR_COMMUNICATION: Communication Error
Well in my scenario(2-Tier Architecture):
I have two Win2k machines on which both Workflow and MQ Series are installed.
i have copied the mqwfchl.tab file(of the server) into the client machine.
when i login to the Workflow Client i get the above error.
Also previously these machines were used as standalone workflow system
So they do have their own mqwfchl.tab file and i havent overwritten the existing files.In the client machine:
The copied server mqwfchl.tab file is in--------> c:\Proj\mqwfchl.tab
also there is the file when the client was used as an standalone
it is in the path c:\program files\mqseries workflow\bin
Also i have defined the Path c:\Proj\mqwfchl.tab in the workflow client config.
Ved,
I even checked whether the server is up and whether i have copied file properly, but still the same error..
All u guys please advice,
Thanks in advance,
Regards,
Hari |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Nov 29, 2002 6:01 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
The simplest check would be:
fmczccc or
fmczccd
When you run this client connections checker on the CLIENT it will resolve the client connections. Run this and see if you are pointing to the right stuff.
Tell us a little more about your configuration. This is how I understood.
2 win2k machines with WF Server
3rd machine with WF Client
You will not have to worry about channel tables if you have a client with Queue Manager.
Also I suspect if the channel tab is in the bin directory:
| Quote: |
t is in the path c:\program files\mqseries workflow\bin
|
It should be in a directory calles "chltabs". Like
c:\program files\mqseries workflow\chltabs.
Copy the channel table in this directory from the server and put it on the client machine.
Did you copy or ftp?
---
Venny |
|
| Back to top |
|
|
| Hari |
| Posted: Fri Nov 29, 2002 6:51 am Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Hi Vennela,
Well first of all i am sorry that i bungled while typing, well i have placed the mqwfchl.tab in the path:
c:\program files\mqseries workflow\chltabs
Well more on the config:
Well there are just 2 Win2K machines (client-server) there is no 3rd machine.
In my previous entry i meant to say that these two machines where acting as STANDALONE WF systems.....now what i did is that i have converted (for my 2-Tier architecture) one of them into a Client.
Well at this present point of time i am not using the Queue Manager of the Client.
Well after using the commands "fmczccd" at the end it gives the following message:
Cannot connect to queue manager FMCQM . --- Queue manager name error.
Please note this the queue manager of the server. So i think there is some problem with this.
Will need to check on this and get back to u.
Thanks once again,
Regards,
Hari |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Nov 29, 2002 7:08 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Hari:
Check your path if you have:
<mqwf-directory>\BIN\MQServer
Try Changing it to:
<mqwf-directory>\BIN\MQClient
This can sometimes be the cause of a problem when changing a Standalone into a client.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Hari |
| Posted: Fri Nov 29, 2002 11:09 pm Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Hi John,
I already have the PATH in place i.e.:<mqwf-directory>\BIN\MQClient
Also have the Mqseries Path set as:
C:\progra~1\mqseri~1\bin\mqclient....
Still I am not able to hunt down the exact problem...
Regards,
Hari |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Nov 30, 2002 8:32 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Hari:
This is a sample output I get when I run client config checker.
| Code: |
C:\>fmczccd
The channel table in the profile is: c:\program files\mqseries workflow\chltabs\
mqwfchl.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 : karthikeya(5010)
TCP/IP-addr : karthikeya
TCP-Port : 5010
Status : ok
---------------
Queue manager : FMCQM1
Protocol : TCP/IP
Connection name : karthikeya(14001)
TCP/IP-addr : karthikeya
TCP-Port : 14001
Status : ok
---------------
You are using the MQSeries Server API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Connecting to the queue manager FMCQM was successful.
There are no checks with this utility to verify that the MQSeries Workflow Serve
r is running on your server. |
Three things you need to look at from the above:
1. "The channel table in the profile" line... double check the file .. is it the file you are inteding to point?
2. "The connect name found in the profile :" -- Are the connect names and QMGR name right?
3. TCP/IP and port....double check.
4. Can you client-connect to the workflow server using the client on the SERVER machine?
If you have done all of those and if you are getting an error saying
"Cannot connect to queue manager FMCQM . --- Queue manager name error" then see if you can ping the IP address of the server from the machine.
I once had a problem where there was a firewall between the client and the server. To make sure there isn't any this is what I would do
on a command prompt :
telnet <serverIPaddress> <MQWF Server Port>
eg telnet karthikeya 5010
(karthikeya is the IP and 5010 is the port number where FMCQM is listening)
If the QMGR is listening on that port and there is no firewall then your window should not come back with any message. If there is a firewall or if the QMGR is not listening then you will get a message like this
| Quote: |
Connecting To karthikeya...Could not open a connection to host on port 5011 : Connect failed
|
I can't think of anything else right now. Why don't you post the results of fmczccd (you may mask the IP).
---
Venny |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Dec 02, 2002 12:55 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I guess this is where your problem is. Your connect names on the client machine that you are trying to connect to workflow should be:
FMCGRP FMCSYS QM ( QM of your client machine) QPREFIX.
"QM name should be the Client QM name."
(I think this is your problem based on a similar problem I had and Vennela's suggestion).
-Laze |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Dec 02, 2002 1:01 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I don't think so.
It's a WF client with MQ Client. There is no Queue Manager at the client.
---
Venny |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Dec 02, 2002 1:14 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Ohh Ok, I did not read his post completely and assumed he was using a MQServer.
After I went through his post, I am thinking he is mixing up the MQServer and MQClient some where in his configuration.
Hari, list the steps sequentially, that you followed when configuring the client. That would most certainly be helpfull.
-Laze |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Dec 02, 2002 1:48 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| mixing up the MQServer and MQClient some where in his configuration |
This can be clarified using the client checker utility. When he runs fmczccd, it would come back saying whether he is using MQ Client API or MQ Server API. I hve listed a sample output above on a client with QueueManager. But it would be almost similar in case of an MQ Client API where it says
You are using the MQSeries Client API for the queue manager communication.
Unfortunately this utility is not available on platforms other than Windows.
But again I too feel very suspicious if there was any residue of the previous setup that he may have to clean up.
---
Venny |
|
| Back to top |
|
|
| Hari |
| Posted: Tue Dec 03, 2002 3:12 am Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
Sorry for replying in late....
Well Venny while using the fmczccd command i get the same specific error mentioned by u....i.e.
"Cannot connect to queue manager FMCQM . --- Queue manager name error"
And also i have looked into the points mentioned by u....and they are all fine.
And definitely i have checked there is no firewall between the client and the server.
Well what i tried out is that if u try connecting to the server from a machine which has only "CLIENTS" components installed, in this case i am able to connect to the server properly.
But if u try to connect to the server via a machine on which all the components of WF are installed (the path for the WF and the MQSeries have been suitably changed to MQClient, to make it act as a client) then i get the FMC_API_ERROR_COMMUNICATION......and am still not able to solve this particular problem.
Regards,
Hari |
|
| Back to top |
|
|
| parsar |
| Posted: Sat Dec 31, 2005 2:39 pm Post subject: |
|
|
Novice
Joined: 08 Dec 2005
Posts: 22
|
Hi
I am exactly in the same situation and my fmczccd output is as follows:
*************************************************************
Logfile used: fmczccd.log
Default configuration used
ShowAll parameter not used
The channel table in the profile is: c:\program files\ibm websphere mq workflow\chltabs\66\mqwfchl.tab
The connect name found in the profile : FMC66.FMCGRP.FMCSYS,FMCQM66
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Channel Name : FMCQM.CL.TCP
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : uitest(14000)
TCP/IP-addr : uitest
TCP-Port : 14000
Status : ok
---------------------
Channel Name : FMCQM66.CL.TCP
Queue manager : FMCQM66
Protocol : TCP/IP
Connection name : ITS-CE00252(14000)
TCP/IP-addr : ITS-CE00252
TCP-Port : 14000
Status : ok
---------------------
You are using the MQSeries Server API for the queue manager communication.
Checking system identifier FMC66.FMCGRP.FMCSYS,FMCQM66 .
Cannot connect to queue manager FMCQM66 . --- FmcFMLException, MQReturnCode=2, MQReasonCode=2085, MQObjectName=FMC66.FMCGRP.FMCSYS.EXE,open, severe admin error
*************************************************************
Any ideas?
Thanks in advance |
|
| Back to top |
|
|
|
|
