Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: DocumentSpecName context property is set incorrectly when you use ESB Toolkit 2.1 for BizTalk Server 2010 or 2013


View products that this article applies to.

Symptoms

Assume that you use Microsoft BizTalk Server 2010 or 2013. When you use a custom pipeline component to call Enterprise Service Bus (ESB) Transformation Service to transform messages in ESB Toolkit 2.1, the DocumentSpecName context property is set incorrectly on the output message, and you receive the following error message:
Log Name: Application
Source: BizTalk Server
Event ID: 5720
Task Category: BizTalk Server
Level: Error
Description:There was a failure executing the send pipeline: "ESBTransform.SendPipeline1, ESBTransform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=ca09cc62b15919a7" Source: "Flat file assembler" Send Port: “<SendPortName>" URI: "<SendPortURI>" Reason: The document type "http://ESBTransform.FlatFileSchema1#TargetRoot" does not match any of the given schemas.

↑ Back to the top


Cause

The issue occurs because ESB Transformation Service does not set the DocumentSpecName context property of the output message to be the target schema type after transformation.

↑ Back to the top


Resolution

Hotfix information

A 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: 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.

Cumulative update information

This issue was first fixed in the following cumulative update of BizTalk Server 2013:

Prerequisites

To apply this hotfix, you must have BizTalk ESB Toolkit 2.1 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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.
File nameFile versionFile sizeDateTimePlatform
Microsoft.Practices.ESB.Itinerary.Services.dll2.1.1.02457613-Oct-201413:11x86

↑ Back to the top


More Information

For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2905255
Revision : 1
Created on : 1/7/2017
Published on : 10/10/2015
Exists online : False
Views : 353