事件类型: 错误
事件来源: XLANG/s
事件种类: 无
事件 ID: 10036
日期: 2010-10-3
事件: 8:02:18
用户: N/A
计算机: DEMO
描述:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service .SAP.OrchGetPickingList.Orch_Get_IDoc_PickList(251bd459-0ad3-c589-35e6-e5f085e5522b)'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 7819f1a6-46ce-4ebd-87b6-9a310a1ed8a4
Shape name:
ShapeId:
Exception thrown from: segment -1, progress -1
Inner exception: Multi-part message 'msgInsertPicklistSyncResponse' has body part 'BodyPart126', expected body part 'BodyPart1'.
Exception type: WrongBodyPartException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void ReadMessageState(Microsoft.XLANGs.Core.Envelope, Microsoft.XLANGs.BaseTypes.XLANGMessage)
The following is a stack trace that identifies the location where the exception occured
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.ReadMessageState(Envelope env, XLANGMessage msg)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.ReceiveMessage(Int32 iOperation, Envelope env, XLANGMessage msg, Correlation[] initCorrelations, Context cxt, Segment s)
at ABB.MobileWH.EAI.SAP.OrchGetPickingList.Orch_Get_IDoc_PickList.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
XML :
<ns0:Request xmlns:ns0="http://pickinglist/SQL/PLPickinglist_Synchronization">
<ns0:sync>
<ns0:after>
<ns0:PLPickinglist_Synchronization UNAME="CNIALIU" WERKS="1501" AUFNR="001010105720" HEADNO="0000003391" POSNR="000000" SOBKZ="" PROJN="ILX-PM00" ITEMNO="6000050431" VBELN="" MATNR="1SBL351001R8011" DISPO="M24" BDMNG=" 1" LGPBE="C52/C54" MAKTX="Contactor A50-30-11 220V-230V50Hz/230-2" LOGGR="WM03" GAMNG=" 1.000" LABST=" 696.000" NODE=" 1" POTX1="" MWHRQ="" SOBVL="" POTX2="" WRKST="" ZPICK="" TaskGu/>
</ns0:after>
</ns0:sync>
</ns0:Request>
Resolution
This issue is a bug, BizTalk Server 2006 has a fix for it. You can get it from here.
After you install this service pack, the issue will be sloved.