| Author |
Message
|
| Luca81 |
 Posted: Tue Feb 19, 2008 2:57 am Post subject: server connection Channel Problem |
 |
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
Hi,
I have this error in the Event Viewer
A protocol error was detected for channel 'OPR.SVRCONN'.
During communications with the remote queue manager, the channel program detected a protocol error. The failure type was 11 with associated data of 0.
Contact the systems administrator who should examine the error logs to determine the cause of the failure.
Sometimes I have also the same error with channel '' (  )
The error is
A protocol error was detected for channel ''.
During communications with the remote queue manager, the channel program detected a protocol error. The failure type was 11 with associated data of 0.
Contact the systems administrator who should examine the error logs to determine the cause of the failure.
What is channel ''?
This is part of the FDC file
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tue February 19 10:58:55 W. Europe Standard Time 2008 |
| Host Name :- SWBIMB10 (Windows Server 2003, Build 3790: Service |
| Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.3 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- RM046045 |
| Application Name :- MQM |
| Component :- rriMQIServer |
| SCCS Info :- lib/remote/amqrsrva.c, 1.153.1.15 |
| Line Number :- 1248 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- E:\Program Files\IBM\WebSphere MQ\bin\amqrmppa.exe |
| Addressing mode :- 32-bit |
| Process :- 00001556 |
| Thread :- 00002219 |
| QueueManager :- SWBIMQC1 |
| ConnId(1) IPCC :- 2914 |
| ConnId(3) QM-P :- 2291 |
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504: A protocol error was detected for channel 'OPR.SVRCONN'. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 112 70 |
| Arith2 :- 64 40
I'm on Windows 2003. MQ version is 6.0.2.3.
Any suggests for resolve this problem?
Thanks a lot |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Feb 19, 2008 3:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could it be that you have a sniffer on the MQ port? 
Or something trying to access the MQ port with a non MQ protocol (telnet ?)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Luca81 |
| Posted: Tue Feb 19, 2008 3:43 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| fjb_saper wrote: |
Could it be that you have a sniffer on the MQ port?
Or something trying to access the MQ port with a non MQ protocol (telnet ?)
Enjoy |
I don't think... We never had this problem.
The server is a virtual machine... And this moorning our system administrators changed the IP... Can it be a dns problem? We are trying to flush the DNS on the clients (ipconfing -flushdns)
 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 19, 2008 4:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
running ipconfig /flushdns on the clients should certainly help.
This could be the root of the problem as the clients are trying to communicate with the old IP. However if the message is being seen on the server side I would make sure that the server has a valid contact with it's domain manager.
We had cases where the virtual server lost contact with the domain manager and access and authentication went to hell.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Luca81 |
| Posted: Tue Feb 19, 2008 4:54 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| fjb_saper wrote: |
running ipconfig /flushdns on the clients should certainly help.
This could be the root of the problem as the clients are trying to communicate with the old IP. However if the message is being seen on the server side I would make sure that the server has a valid contact with it's domain manager.
We had cases where the virtual server lost contact with the domain manager and access and authentication went to hell.
Enjoy |
Thx a lot fjb_saper. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Feb 20, 2008 10:27 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Did the problem go away? If not, could you please PM me the *whole* FDC... That was new code added in 6.0.2.3, and I just wanted to see what was being received.
Do you know what code (language and MQ fixpack level) was on the other end of the client channel? |
|
| Back to top |
|
|
| Luca81 |
| Posted: Wed Mar 12, 2008 12:50 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| JasonE wrote: |
Did the problem go away? If not, could you please PM me the *whole* FDC... That was new code added in 6.0.2.3, and I just wanted to see what was being received.
Do you know what code (language and MQ fixpack level) was on the other end of the client channel? |
Problem was solved with an easy flush.
thx |
|
| Back to top |
|
|
| Il_Ciclone |
| Posted: Tue Jun 24, 2008 4:37 am Post subject: |
|
|
Novice
Joined: 21 Mar 2007
Posts: 24
|
Im getting this as well:
A protocol error was detected for channel 'myChannel'.
During communications with the remote queue manager, the channel program detected a protocol error. The failure type was 11 with associated data of 0.
I'm writing an XMS app (IA9H 1.2.6.0) on a PC with a WMQ 6.0.2.0 client
and the server is Win2k3 on 6.0.2.3 (p600-203-080123)
I actually get the same error towards 2 separate machines with the same patch level.
Im now upgrading the client to 6.0.2.3 now to see if it helps.
I´ll let you know if i solve it, and if you still want the FDC i can send it Jason. |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Jun 24, 2008 4:50 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Yes - please pm me the whole fdc (or pm me your email addr) and I'll take a look. Is your xms app in .net or c? |
|
| Back to top |
|
|
| Il_Ciclone |
| Posted: Tue Jun 24, 2008 5:02 am Post subject: |
|
|
Novice
Joined: 21 Mar 2007
Posts: 24
|
| JasonE wrote: |
| Yes - please pm me the whole fdc (or pm me your email addr) and I'll take a look. Is your xms app in .net or c? |
It´s in .Net and you´ve got a PM with the FDC  |
|
| Back to top |
|
|
| Il_Ciclone |
| Posted: Tue Jun 24, 2008 5:13 am Post subject: |
|
|
Novice
Joined: 21 Mar 2007
Posts: 24
|
Once i upgraded my client to 6.0.2.3 it works like a breeze. Problem solved.
Working setup:
6.0.2.3 Client -> 6.0.2.3 Server
Failing setup:
6.0.2.0 Client -> 6.0.2.3 Server
thanks |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Jun 24, 2008 6:58 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Yeah - you hit internal defect 116273, which arose when another defect added validation to the inbound data to tighten up on some unchecked fields. Basically 6.0.2.3 enforces that various length fields are exactly as specified, and this broke the fully managed MQ .net clients MQINQ functionality (possibly called under the covers at connect time, not sure), which was actually miscalculating one of the field lengths. The fix to this also shipped in 6.0.2.3, but does mean if you need to connect in fully managed .net clients then you need 6.0.2.3 on both ends of the loop.
I did notice that this was not documented externally - I've raised IC57019 to document this, and I will see if its possible to tollerate the miscalculation rather than throwing the error or whether this just needs documenting.
Thanks for the information! |
|
| Back to top |
|
|
| spazy |
| Posted: Tue Dec 14, 2010 10:58 am Post subject: |
|
|
Newbie
Joined: 02 Sep 2008
Posts: 8
|
hello guys,
i have same problem with one systems win2k8 64bit MQ client 7.0.1.0.
MQ server 6.0.2.8.
Interesting thing is that in application level everthing looks correctly, but FDC log has now 4.5 GB 
repeating message is:
-------------------------------------
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Łt prosinec 14 2010 09:40:45 Central Europe Standard |
| UTC Time :- 1292316045.977000 |
| UTC Time Offset :- 60 (Central Europe Standard Time) |
| Host Name :- CAP |
| Operating System :- Windows Server 2008 Server Standard x64 Edition, Build |
| 6002: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- RM496003 |
| Application Name :- MQM |
| Component :- reqMakeCall |
| SCCS Info :- lib/client/amqrcafa.c, 1.220 |
| Line Number :- 5391 |
| Build Date :- Aug 13 2009 |
| CMVC level :- p000-L090813 |
| Build Type :- IKAP - (Production) |
| UserID :- SYSTEM |
| Process Name :- C:\Program Files (x86)\Sevice\Client\binnt\Qui |
| ckModule.exe |
| Addressing mode :- 32-bit |
| Process :- 00002992 |
| Thread :- 00000406 |
| UserApp :- TRUE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504: Byla zjiÅ¡těna chyba protokolu u kanálu ''. |
| FDCSequenceNumber :- 21517 |
| |
+-----------------------------------------------------------------------------+
Havent you another ideas? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 14, 2010 11:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| spazy wrote: |
i have same problem with one systems win2k8 64bit MQ client 7.0.1.0.
MQ server 6.0.2.8 |
No you don't. You have a similar problem, but the original 2 year old thread refered to WMQv6.2.0.0. This is why we discourage the reopening of old threads; refer to the old one if you think it's relevent but it's not the same problem. Especially as the old problem was resolved by upgrading the client. Which you're clearly done.
| spazy wrote: |
| Havent you another ideas? |
Aside from actually describing the problem so we can help? Such as what kind of .NET connection you're using, why you're not using the v7.0.1.3 client or queue manager, at what point the FDC is raised & if you have a PMR open?
No, no other ideas.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
