FIX: You receive an "Exception Caught: Cannot use a prefix with an empty namespace" error message when you use a Transform shape to generate a map in BizTalk Server 2004 SP1

This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Transform shape in a Microsoft BizTalk Server Orchestration to generate a map file after you have installed BizTalk Server 2004 Service Pack 1 (SP1), you may receive the following error message when you try to validate the map:
Exception Caught: Cannot use a prefix with an empty namespace.
Note This problem does not occur in BizTalk Server 2004 without SP1 installed.
This problem occurs when you provide multiple source inputs for the map and the source schemas do not have a Target Namespace property specified. Therefore, the generated map will contain a namespace attribute that is null. When the Target Namespace property is not specified, the map generation process should not put the namespace attribute in the map.
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 Web site: 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.


Microsoft BizTalk Server 2004 Service Pack 1 (SP1) is required.

Restart requirement

You must restart your 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 tool in Control Panel.
   Date         Time   Version     Size       File name   ------------------------------------------------------------------------------------------   02-Mar-2005  03:12  3.0.6107.0    684,544  Btsxmltools.dll     02-Mar-2005  08:13  3.0.6107.0    221,184  Microsoft.biztalk.artifactbrowser.dll     02-Mar-2005  08:13  3.0.6107.0    274,432  Microsoft.biztalk.basefunctoids.dll     02-Mar-2005  08:13  3.0.6107.0     45,056  Microsoft.biztalk.crossreferencing.dll     02-Mar-2005  08:13  3.0.6107.0     40,960  Microsoft.biztalk.crossreferencingfunctoids.dll     02-Mar-2005  08:13  3.0.6107.0    249,856  Microsoft.biztalk.mapper.dll     02-Mar-2005  08:13  3.0.6107.0  1,114,112  Microsoft.biztalk.tom.dll  
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Steps to reproduce the behavior

  1. In Microsoft Visual Studio .NET, create a new BizTalk Server project.
  2. Create a new schema, and then set the Target Namespace property to nothing.
  3. Create a new BizTalk Server Orchestration, and then create three new message types.
  4. Set the Identifier property for the three message types to the following values:
    • Source1
    • Source2
    • Destination1
  5. For each message type that you created in step 3, set the Message Type property to the schema that you created in step 2.
  6. Add a Transform shape to the orchestration.
  7. Right-click the Transform shape that you added, and then click Configure Transform Shape.
  8. In the Transform configuration dialog box, set two Source messages to Source1 and Source2, set one Destination message to Destination1, and then click OK.
  9. In Solution Explorer, right-click the map that you generated in step 8, and then click Validate Map.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 894177 - Last Review: 10/27/2013 07:30:36 - Revision: 3.4

  • Microsoft BizTalk Server 2004 Service Pack 1
  • kbnosurvey kbarchive kbautohotfix kbbiztalk2004sp2fix kbqfe kbbug kbfix kbprb kbhotfixserver KB894177