| Author |
Message
|
| jayffic |
 Posted: Tue Jun 17, 2003 8:38 am Post subject: Help please - Error-No:1505 |
 |
|
Novice
Joined: 12 Mar 2003
Posts: 12
|
We are using v3.2 and everything appears to be installed correctly (MQ, DB, Work flow). However, when I try to log on to the client, I receive a message box with this error:
FMC_API_ERROR_COMMUNICATION: Communication error.
We thought this was related to the MQSERVER variable being set on the server, so we nulled it (MQSERVER=) and now we receive another error:
(Message box title:) IBM MQSeries Workflow
Error-No: 1505
main():1500:FMC_METHOD_EXCEPTION
ExecutionService::LogonWithOptions
Any help is greatly appreciated.
Thank you,
Jay |
|
| Back to top |
|
 |
| Ratan |
| Posted: Tue Jun 17, 2003 8:59 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
what is the OS and also how did you setup your workflow server? Make sure all the versions are compatible (MQ, DB2 and workflow).
_________________
-Ratan |
|
| Back to top |
|
|
| jayffic |
| Posted: Tue Jun 17, 2003 11:14 am Post subject: |
|
|
Novice
Joined: 12 Mar 2003
Posts: 12
|
Thanks for the quick reply.
The OS is NT.
It was actually working for one moment (a couple of Client connections) and then started receiving this error.
So everything is compatible, and it's probably something I did, or has been corrupted.
Question is how to find it and fix it when this error does not appear to produce a log?
Is there a way to test that the port is working correctly?
This is a separate, but related problem (which may confuse rather than help, so disregard at your discretion). When deleted and tried to recreate the queue manager through the configuration tool, I receive these message boxes:
(title) MQSeries Workflow Configuration
FMC33149E Return code from runmqsc FMCQM <"e:\fmcwinnt\qmgrs\fmcqm\mqs\fmczcltc.mqs">>
"e:\fmcwinnt\cfgs\fmc\log\fmcqm.log" is: -1073741819
and
(same title)
FMC33903E Error while creating MQSeries queue manager FMCQM occurred.
See log file "e:\fmcwinnt\cfgs\fmc\log\@fmcqqm.log" log for more information.
I look a the logs but they say nothing specific, just repeat what the message boxes say.
Thanks again. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jun 17, 2003 11:26 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
Is there a way to test that the port is working correctly?
|
On the server:
netstat -na and look for the port of your interest and see if it is listening. If two clients can connect and the third one cannot thn there is something wrong with the third client
From the client:
telnet <server hostname> <port>
If you get a connection then the TCP communication is good. Eles there is something wrong
What sort of setup are you talking about
Server on one machine and clients on different machine? or How?
You should search for this error
FMC_API_ERROR_COMMUNICATION and you will find lot of reasons why you get this error. Most likely, the communication between the server and the client is not right.
How(and where) did you setup the client?
Also what versions of MQ, MQWF, DB2, Windows?
-------
Venny |
|
| Back to top |
|
|
| jayffic |
| Posted: Tue Jun 17, 2003 12:10 pm Post subject: |
|
|
Novice
Joined: 12 Mar 2003
Posts: 12
|
Thanks for the reply.
I connected to the machine via telnet using the port 5010.
The netstat says TCP 0.0.0.0:5010 0.0.0.0:0000 LISTENING.
Can I assume the server is running since the port connected? And why isn't the server responding or logging errors if it is connected?
The set up is:
Machine 1
Server
Client
Machine 2
Client
Machine 3
Client
All of them get the error.
Versions:
MQWF: 3.2.2
DB2: 6
OS: NT 4 SP 6
MQ: 5.2.1
I looked up the error and could not find a solution. I did find stuff to try though none of it worked.
Thanks |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jun 17, 2003 12:26 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Can you write a quick little Java (or C or C++) program to just do a logon, then logoff.
The 1500 series of return codes is unique to ActiveX api, and thus the cause of this could be that the MQWorkflow control is not configured properly, if you can access the Server using any other API, I would start looking more closely at how you are setting up the MQWorkflow control.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jun 17, 2003 12:42 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If the port is in LISTENING then it does not mean the server is up. It means the listener of the workflow MQGR is running.
Most likely your server is not up.
Can you verify these:
In the windows services, workflow is showing started
Do a process listing and see if fmcamain, fmcemain etc processes are running.
I have not worked with those versions of software and to tell you the truth, you are atleast 2 years behind.
-------
Venny |
|
| Back to top |
|
|
| jayffic |
| Posted: Tue Jun 17, 2003 4:05 pm Post subject: |
|
|
Novice
Joined: 12 Mar 2003
Posts: 12
|
Sure, rub it in  ... Anyway...
Turns out the channel table had two queue manager entries in it for the same port. It was still trying to use the old queue manager.
Probably from me trying different configurations trying to get something...anything to work. Work flow (or this ...old... version) does not clean up after itself well.
Not sure why the (potential) AtiveX error occurred (probably a feature).
Well, thanks for the help and now I'll see about creating flows... |
|
| Back to top |
|
|
|
|
