Article ID: 2388784 - Last Review: May 7, 2011 - Revision: 4.0 Hotfix to add the "ReceivedIdocRelease" binding property for the WCF-SAP adapter to BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010
On This PageThis article applies to the following product:
IntroductionThis article describes a hotfix for Microsoft BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010. This hotfix adds the ReceivedIdocRelease binding property to the Microsoft Windows Communication Foundation (WCF)-based SAP adapter. This property is used to resolve the following issue. SymptomConsider the following scenario:
Event Type: Error Event Source: <BizTalk Server version> Event Category: <BizTalk Server version> Event ID: 5719 Description: There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "<Receive Port>" URI: "<URI>" Reason: Finding the document specification by message type "<schema namespace>" failed. Verify the schema deployed properly. A message sent to adapter "WCF-SAP" on send port "<send port>" with URI "<URI>" is suspended. Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: <Segment name> IDOCTYP: <IDOCTYP> Release: <release> CIMTYP: . Ensure that your message xml validates against the operation schema. CauseThis issue occurs because the WCF-based SAP adapter incorrectly uses the DOCREL property of the IDOCs to determine the release number of the IDOCs that are sent. SAP populates the DOCREL property with the current value of SYSEREL. When SAP is upgraded, the WCF-based SAP adapter uses this new value of DOCREL to determine the IDOC release number. However, the release number from this new value is the previous release number. Therefore, the release number from this new value is incorrect for the IDOCs that are sent. NoteDOCREL is an SAP release number for IDOC. RESOLUTIONTo resolve this issue after you apply the following hotfix, edit the ReceivedIdocRelease binding property. For more information about how to edit the ReceivedIdocRelease binding property, see the "More Information" section. Cumulative update informationBizTalk Adapter Pack 2010The hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Adapter Pack 2010.For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 2539794 (http://support.microsoft.com/kb/2539794/ ) Cumulative update package 1 for BizTalk Adapter Pack 2010 BizTalk Adapter Pack 2.0A specific hotfix is available to resolve this issue. This hotfix is available individually and is included in Cumulative Update 1 for BizTalk Adapter Pack 2.0.For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 2444952
(http://support.microsoft.com/kb/2444952/
)
Cumulative update package 1 for BizTalk Adapter Pack 2.0 Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, you must have BizTalk Adapter Pack 2.0 installed.Restart requirementAfter you apply this hotfix, you do not have to restart the computer.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.For all supported x86-based versions of BizTalk Adapter Pack 2.0Collapse this table
For all supported x64-based versions of BizTalk Adapter Pack 2.0Collapse this table
MORE INFORMATIONHow to edit the ReceivedIdocRelease binding propertyTo edit the ReceivedIdocRelease binding property, use the appropriate value that meets one of the following conditions:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor more information about how to receive SAP IDOCs in BizTalk Server, visit the following Microsoft Developer Network (MSDN) website: How to receive SAP IDOCs in BizTalk Server
(http://msdn.microsoft.com/en-us/library/cc185169(BTS.10).aspx)
For more information about how to use BizTalk Server to send IDOCs to SAP, visit the following MSDN website:How to use BizTalk Server to send IDOCs to SAP
(http://msdn.microsoft.com/en-us/library/dd788567(BTS.10).aspx)
| Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top