Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 945235 - Last Review: March 26, 2008 - Revision: 1.2
Error message after you install BizTalk Accelerator for SWIFT Message Pack 2007: "Event ID: 10001 Failed while creating a orchestration.assembly.name service"
After you install Microsoft BizTalk Accelerator for SWIFT Message Pack 2007, you receive an error message that resembles the following message when you are running an orchestration instance that tries to rehydrate:
Event Type:
Error Event Source: XLANG/s
Event Category: None
Event ID: 10001
Date: 18/10/2007
Time: 12:12:08
User: N/A
Computer: BIZTALKSRV
Description: Failed while creating a orchestration.assembly.name service.
Exception type: ServiceCreationException
Additional error information: Object cannot be stored in an array of this type.
Exception type: InvalidCastException
Source: mscorlib
Target Site: Void InternalSetValue(Void*, System.Object)
This problem occurs if you have a dehydrated orchestration instance that contains both of the following references:
- A reference to version 3.1.0.0 or an earlier version of the Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.dll file.
- A reference to an assembly that contains schemas that use a Message Pack version that is earlier than Message Pack 2007.
When a new message arrives after you deploy Message Pack 2007, the new Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.dll file receives the message. Any assemblies that are compiled use the Message Pack 2007 schemas.
When the orchestration instance tries to receive this message, the assembly or the schema structure that the BizTalk message engine receives is not the assembly or the schema structure that the orchestration instance expects.
To resolve this problem, follow these steps:
- Unenlist all orchestration instances that have been compiled by using schemas from Message Pack versions that are earlier than Message Pack 2007 and schemas from version 3.1.0.0 or an earlier version of the Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.dll file. Also, remove all receive port bindings for these orchestration instances.
Note This step allows for currently executing orchestration instances to be completed. However, this step prevents these orchestration instances from receiving any new messages. - Create a new version of your schema assembly. Make sure that the version number (1.1.x.x) contains the updated message type schemas that your environment uses.
- Build and deploy this new schema assembly.
- Create a new version of the orchestration instance. Make sure that the version number (1.1.x.x) is larger than the version number of the previous orchestration instance. Then, reference the new Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.dll file and the updated schema assembly that step 3 mentions.
- Build and deploy the new orchestration instance.
- Bind your receive ports to the new orchestration instance that step 4 mentions, and then start the orchestration instance. This orchestration instance can now correctly handle any new received messages.
The following versions of the Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.dll file may cause the problem:
- Version 2.0.0.0, which is included in BizTalk Accelerator for Swift 2.3 Service Pack 1.
- Version 2.5.0.0, which is included in Message Pack 2006.
- Version 3.1.0.0, which is included in Message Pack 2007.
You must perform the resolution any time you upgrade to a newer version of the Microsoft.Solutions.FinancialServices.SWIFT.RuntimeSchemas.dll file or to a new Message Pack.
APPLIES TO
- Microsoft BizTalk Accelerator for SWIFT 2.3 Standard Edition
- Microsoft BizTalk Accelerator for SWIFT 2.3 Enterprise Edition
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
| kbtshoot kbexpertiseadvanced kbbug KB945235 |
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