FIX: Event ID: 10034 may be logged when you use BizTalk Accelerator for SWIFT 3.0 together with a 64-bit version of BizTalk Server 2006 R2 on a computer that is running a 64-bit version of Windows Server 2003

Consider the following scenario:

• You use Microsoft BizTalk Accelerator for SWIFT 3.0 together with a 64-bit version of Microsoft BizTalk Server 2006 R2.
• The 64-bit version of BizTalk Server 2006 R2 is installed on a computer that is running a 64-bit version of Windows Server 2003.
• You call the Message Repair function.

In this scenario, an Error event that resembles the following may be logged in the Application log:

Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10034
Description:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'MrsrRepairService.MrsrRepair(77d3725d-f60d-df05-28c9-81c04f7569c5)'. 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: <InstanceID>
Shape name: InitializeMrsrHelper
ShapeId: 1a486615-9df0-4f7e-8e84-22d50ee800cf
Exception thrown from: segment 1, progress 36
Inner exception: Value cannot be null.
Parameter name: <name>
Exception type: ArgumentNullException
Source: mscorlib
Target Site: System.String ExpandEnvironmentVariables(System.String)
The following is a stack trace that identifies the location where the exception occured
at System.Environment.ExpandEnvironmentVariables(String name)
at Microsoft.Solutions.FinancialServices.SWIFT.MrsrHelper.MrsrHelper..ctor(String departmentName, Boolean isNewSubmission, String correlationId)
at Microsoft.Solutions.FinancialServices.SWIFT.MrsrHelper.MrsrUtil.Initialize(XmlDocument messageDoc, Boolean isNewSubmission, String correlationId, Boolean unParsed)
at MrsrRepairService.MrsrRepair.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp

Note In this Error event, the word "occured" is a misspelling for the word "occurred."

This problem occurs because the following registry subkey does not exist in the registry:Note The BizTalk Accelerator for SWIFT 3.0 Installation Wizard creates the following registry subkey to store the configuration settings:However, the BizTalk Server runtime engine looks for the following registry subkey:

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Accelerator for SWIFT 3.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the following products installed to apply this hotfix:

• A 64-bit version of BizTalk Server 2006 R2
• A 64-bit version of Windows Server 2003
• BizTalk Accelerator for SWIFT 3.0

Restart requirement

You do not have to restart the 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 item in Control Panel.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: