| Author |
Message
|
| jpeela |
 Posted: Wed Apr 11, 2007 12:32 am Post subject: amq4048 |
 |
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi all,
We had a problem while pinging the channel.Which throws an unexpected error with amq4048.
There is also an FDC created.which is as follows.
|
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed April 11 14:43:56 Malay Peninsula Standard Time 2 |
| Host Name :- EAPSDEV10066 (Windows Ver 5.2 Build 3790: Service Pack |
| 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MS099001 |
| Application Name :- MQM |
| Component :- HandleBadMQAIResponse |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- srvadmin |
| Process Name :- C:\WINNT\system32\mmc.exe |
| Process :- 00004600 |
| Thread :- 00000002 |
| QueueManager :- QMACP!UJP!POS!REG!MBK |
| Major Errorcode :- xecF_E_UNEXPECTED_SWITCH |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6120 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6120: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2195 893 |
| |
+--------------------------
I have googled for the error and gone through the ibm site where in it asks for MUSR_MQADMIN for the administrative rights.We have included the MUSR_MQADMIN in the administrators group and the user srvadmin also is in the administrator group as well as mqmq group.
but still we get the same unexpected error.
from the forum I have searced for amq4048 from which i suppose the problem is with the listener or network.Actually the listener is running.
We were able to ping the other machine aswell as telnet to the port.
But now I cannot go for a higher CSD now.It is as per the instructions.And so I cannot update to the higher CSD.
Can some one helpout with this.
Awaiting your reply.
Thanks in advance.
_________________
Jogi |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Wed Apr 11, 2007 12:46 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| jpeela |
| Posted: Wed Apr 11, 2007 1:26 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi Michael Dag,
Ya I have pinged the chjannel from explorer, which gave the error amq4048.But i am able to ping the machine from command prompt and even able to telnet to the port.
Awaiting ur reply,
thanks in advance.
_________________
Jogi |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Apr 11, 2007 1:32 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| jpeela wrote: |
But i am able to ping the machine from command prompt and even able to telnet to the port.
|
ping the channel from the runmqsc commandline, it should work. this amq4048 is an irritating mmc 'thingy'
let me know if it works from runmqsc
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jpeela |
| Posted: Wed Apr 11, 2007 2:06 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi Michael ,
When I tried pinging the channel from the command prompt its giving the folowing error
2 : ping channel(CHUUJPPOS.REGMBK)
AMQ9558: Remote Channel is not currently available.
but actually the listener and the quemanager are running fine on th eother machine.And we are able to ping aswellas telnet to the port of the machine.
Awaiting your reply.
thanks in advance
_________________
Jogi |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Apr 11, 2007 2:09 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
at least you don't get the AMQ4048 anymore...
post the definition of the channel and ask the definition from the other side, there maybe a conflict in name, they have to have the same name... 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jpeela |
| Posted: Wed Apr 11, 2007 2:19 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
Hi Michael,
thanks for your advise and suggessions.Actually the cxhannel was existing there but it was in the stoped state.So I have started from the other side.so it came to inactive state.And now I have reset the channel and started.But what about the FDC created.So is that a simple bug.Or is there anything else.
Thanks in advance.
_________________
Jogi |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Apr 11, 2007 2:31 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| jpeela wrote: |
Hi Michael,
thanks for your advise and suggessions.Actually the cxhannel was existing there but it was in the stoped state.So I have started from the other side.so it came to inactive state.And now I have reset the channel and started. |
Good
| jpeela wrote: |
| But what about the FDC created.So is that a simple bug.Or is there anything else. |
I just call it the MMC 'thingy' sometimes it happens sometimes not, you can try it now, now that the ping is working...
I always ping from runmqsc, just to be sure...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jpeela |
| Posted: Wed Apr 11, 2007 2:38 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
Hi michael,
Thanks for all your help.So I need not worry of this FDC any more.Thanks again.
_________________
Jogi |
|
| Back to top |
|
|
|
|
