| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Login problems with thick client. |
« View previous topic :: View next topic » |
| Author |
Message
|
| mike_mq |
 Posted: Mon Oct 20, 2003 4:33 am Post subject: Login problems with thick client. |
 |
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
Hello,
I am having problems while logging MQWF Client (thick). It is giving error "FMC_API_ERROR_COMMUNICATION:Communication error." I would appreciate if anyone can help me to resolve this.
Best Regards,
Mike. |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Oct 20, 2003 5:23 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Most likely there is an error either with connect parameters or with your channel table.
Run the client checker and see if there are any errors. If you can't figure out what the errors mean post the results here.
On a windows command prompt run
fmczccd
-------
Venny |
|
| Back to top |
|
|
| mike_mq |
| Posted: Mon Oct 20, 2003 12:42 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
Thanks for the response Mr. Venny.
When I typed "fmczccd" on prompt, it was saying that channel table exists and giving all the information of the table file including Queue manager, Protocol..etc.
Also showing that "cannot connect to queue manager FMCQM. --- Queue manager not available".
Then, when I was trying to start FMCQM using Command Prompt, a warning window popped up. That is
"This application has failed to start because DB2APP.dll was not found.
Re-installing the application may fix this problem."
So, now I am thinking to reinstall DB2 and MQWorkflow. What do you suggest me.
Appreciate your help.
Best Regards,
Mike. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Oct 20, 2003 12:54 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
That means the Queue Manager for workflow was not started in first place (workflow ofcourse was not started). I was of the false assumption that client and server were on different boxes. I am not sure what to suggest.
If I were you I would delete the configuration, uninstall workflow, uninstall MQ and DB2, cleanup registry and start off afresh.
But, after each of DB2, WMQ and WMQWF installations, I would verify the respective product is working fine. (For each of the products, there is a quick installation verification procedure in their installation guides).
Also, it would help us and you in getting a quick answer if you can also let us know the architecture (3-tier, 2-tier, stand alone etc), product versions, fixes applied and OS. |
|
| Back to top |
|
|
| mike_mq |
| Posted: Mon Oct 20, 2003 1:09 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
My apologies for not being in proper formatting of the question and for delayed communication. From now onwards, I will do it in a right way. Now, I am going to uninstall all the components (MQWF and DB2) and install them in proper order.
Thank you
Mike.
P.S: I am using windows OS, DB2 7.1 and MQWF 3.3.2. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
