This article has been archived. It is offered "as is" and will no longer be updated.
Error message description
You use Microsoft BizTalk Accelerator for SWIFT 3.0 together with Microsoft BizTalk Server 2006 R2. You drop a SWIFT message together with a Business Rules Engine (BRE) validation error at the receive location in the instance of BizTalk Server. You enable the StaticSupport registry subkey to call static methods from BRE.
An Error event that resembles the following is logged:
Event Type: Error 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: 93fec8bc-172e-4050-adc2-36399685e8e3 Shape name: InitializeMrsrHelper ShapeId: 1a486615-9df0-4f7e-8e84-22d50ee800cf Exception thrown from: segment 1, progress 36 Inner exception: No user object is associated with rule "MRSRWorkFlowRule".
Exception type: RuleSetTranslationUserObjectMissingException Source: Microsoft.Solutions.FinancialServices.SWIFT.MrsrHelper Target Site: System.String CallBreRules(System.Xml.XmlDocument, System.String ByRef) The following is a stack trace that identifies the location where the exception occured
at Microsoft.Solutions.FinancialServices.SWIFT.MrsrHelper.MrsrUtil.CallBreRules(XmlDocument messageDoc, String& retErrorString) 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)
To resolve this problem by using a hotfix, see the "Resolution" section. To work around this problem by changing the registry, see the "Workaround" section.
Note For more information about the StaticSupport registry subkey, visit the following Microsoft Web site:
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.
You must have BizTalk Server 2006 R2 and BizTalk Accelerator for Swift 3.0 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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.
To work around this problem, disable the StaticSupport registry subkey. To have us do this for you, go to the "Fix it for me" section. If you’d rather do this yourself, go to the "Let me fix it myself" section.
Fix it for me
To run this workaround automatically, click the Fix this problemlink. Then click Runin the File Downloaddialog box, and follow the steps in this wizard.
Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD, and then you can run it on the computer that has the problem.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To work around this problem, disable the StaticSupport registry subkey. To do this, follow these steps:
Click Start, click Run, type regedit , and then click OK.
Locate and then right-click the following registry subkey:
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