Microsoft KB Archive Search

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.

  1. Home
  2. Error message when you use a map to transform messages in a BizTalk Server orchestration: "Uncaught exception (see the 'inner exception' below) has suspended an instance of service"

Error message when you use a map to transform messages in a BizTalk Server orchestration: "Uncaught exception (see the 'inner exception' below) has suspended an instance of service"

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a map in a Microsoft BizTalk Server project.
  • The map uses an XSL for Transformations (XSLT) file that is defined in the Custom XSL Path Grid Properties.
  • The map uses the XSLT file to transform messages.
  • You use the map in an orchestration to process messages.
In this scenario, messages may be suspended. Additionally, you may receive an error message that resembles the following in the Application log:
Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10030
Description: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'BizTalk orchestration'. 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: instance id
Shape name: shape name
ShapeId: shape id
Exception thrown from: segment number, progress number
Inner exception: Error encountered while executing the transform project name.map name. Error:Unable to create the transform.
The "Additional error information" section of the error message contains error information that resembles the following:
Resolving of external URIs was prohibited.

↑ Back to the top

Cause

This issue can occur if the XSLT file that is defined in the Custom XSL Path Grid Properties uses the <xsl:import> element or the <xsl:include> element to import or to include an external XSLT file.

↑ Back to the top

Workaround

To work around this issue, make sure that the XSLT file that is defined in the Custom XSL Path Grid Properties contains all the code that is required to transform the message.

↑ Back to the top

Status

This behavior is by design.

↑ Back to the top

More information

The <xsl:import> element is used to import an external XSLT file. The <xsl:include> element is used to include an external XSLT file. You cannot use these elements in custom XSLT files that are defined in the Custom XSL Path Grid Properties in a BizTalk project. You cannot do this because a Uniform Resource Identifier (URI) that is defined in an external XSLT file may be from a nonsecure source such as the Internet.

↑ Back to the top

Keywords: kbbtsorchestration, kbbtsmapper, kbbts, kbtshoot, kbprb, KB945924

↑ Back to the top

Article Info
Article ID : 945924
Revision : 5
Created on : 1/14/2008
Published on : 1/14/2008
Exists online : False
Views : 471