| Author |
Message
|
| Surfer |
 Posted: Wed Feb 02, 2005 1:28 pm Post subject: FMC_API_ERROR_INTERNAL |
 |
|
Apprentice
Joined: 14 Jun 2002
Posts: 31
|
I install only:
- MQSeries 5.3 client
- WF 3.4 and fix pack (only runtime)
On windows XP professional
After configuration (with the MQWFCHL.TAB from the server AIX) everything seems to go in a nice way after. The command fmczccd -y FMC says that all is OK.
But when I tryed to launch the client FMC on windows an error message is displayed:
FMC_API_ERROR_INTERNAL.
Could anyone help please ?
THank you. |
|
| Back to top |
|
 |
| hos |
| Posted: Thu Feb 03, 2005 7:23 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Are you running MQWF server on AIX and client on Windows XP?
You should apply the latest ServicePack (SP6) on both machines. There was a bug in V3.4 that caused such an error. |
|
| Back to top |
|
|
| Surfer |
| Posted: Thu Feb 03, 2005 7:43 am Post subject: |
|
|
Apprentice
Joined: 14 Jun 2002
Posts: 31
|
Yes :
MQWF server on AIX and Client on windows XP.
Thank you very much, I will try that then I will let you a message here. |
|
| Back to top |
|
|
| Surfer |
| Posted: Thu Feb 03, 2005 8:34 am Post subject: |
|
|
Apprentice
Joined: 14 Jun 2002
Posts: 31
|
Hi,
I installed the SP6 (for workflow 3.4) the I reboot the system.
Then I create a new fmc
When launching the Client, the error is still there: same error message as before.
Is that a conflict between addresses?
When I run C:\Documents and Settings\galaxia>fmczccd -y FMC
I have this results now.
---------------------------------------------------result--------------------
C:\Documents and Settings\galaxia>fmczccd -y FMC
The channel table in the profile is: C:\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 : 10.16.5.85(5010)
TCP/IP-addr : 10.16.5.85
TCP-Port : 5010
---------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Ping to server 10.16.5.85 was successful.
The specified module could not be found.
------------------- Exception occurred--------------------------------
2005-02-03 16:10:55.062000
Exception code: 0xc0000005 ACCESS_VIOLATION
Fault address: 0x4e55305b 0x01:0x0000205b C:\Program Files\IBM\WebSphere MQ\bin\AMQ
Registers:
EAX: 0x00001010 CS: 0x001b EIP: 0x4e55305b FLG: 0x00010246
EBX: 0x0012c654 SS: 0x0023 ESP: 0x0012c394 EBP: 0x00001000
ECX: 0x0012c654 DS: 0x0023 ESI: 0x00796c18 FS: 0x0038
EDX: 0x77e7abf1 ES: 0x0023 EDI: 0x00794008 GS: 0x0000
Call stack:
Address Frame Logical addr Module
4e55305b 00001000 0001:0000205b C:\Program Files\IBM\WebSphere MQ\bin\AMQRMQIA.dll
------------------- End of Exception --------------------------------
-----------------------------------------------end of result-------------------- |
|
| Back to top |
|
|
| hos |
| Posted: Mon Feb 07, 2005 1:58 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
you should use the configuration checker fmczchk to check the sanity of your installation.
You should also check the service level of MQ. Enter MQVER on the command line. You should have MQ Version 530.7 (CSD7).
If that doesn't help I suggest to open a PMR and contact the support team. |
|
| Back to top |
|
|
|
|
