Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 945924 - Last Review: January 14, 2008 - Revision: 1.4
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"
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.
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.
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.
This behavior is by design.
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.
APPLIES TO
- Microsoft BizTalk Server 2006 R2 Standard Edition
- Microsoft BizTalk Server 2006 R2 Enterprise Edition
- Microsoft BizTalk Server 2006 R2 Developer Edition
- Microsoft BizTalk Server 2006 R2 Branch Edition
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2004 Service Pack 2
- Microsoft BizTalk Server 2004 Service Pack 1
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Partner Edition
| kbbtsorchestration kbbtsmapper kbbts kbtshoot kbprb KB945924 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate