FIX: Custom extension XML is not saved in the map file in a BizTalk Server solution

Gilt für: BizTalk Server 2013 R2 BranchBizTalk Server 2013 R2 DeveloperBizTalk Server 2013 R2 Enterprise


Consider the following scenario:

  • You deploy a map in a Microsoft BizTalk Server solution.
  • You add a custom extension XML file to your solution by selecting the custom extension XML file for the Custom Extension XML property in the Grid properties of the map.
  • You save the revised map, and then you close and reopen it. 
In this scenario, the extension is not saved as expected. You expect that the map will contain the following segment:

<CustomXSLT XsltPath="" ExtObjXmlPath="YouCustomExtentionXMLFile" />
Additionally, when you proceed to build, deploy, and configure the solution, you may receive the following error message:

The Messaging Engine failed while executing the inbound map for the message coming from source URL:"SourceURL" with the Message Type MessageType;. Details:"Cannot find the script or external object that implements prefix 'ScriptNS0'."


Cumulative update information

BizTalk Server 2013 R2

The fix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2013 R2.

BizTalk Server 2013

The fix that resolves this issue is included in Cumulative Update 3 for BizTalk Server 2013.


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


For information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server .

For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support .