Article ID: 950536 - View products that this article applies to.
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:
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.
Event Type: Error
Event Category: None
Event ID: 10034
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.
Shape name: InitializeMrsrHelper
Exception thrown from: segment 1, progress 36
Inner exception: No user object is associated with rule "MRSRWorkFlowRule".
Exception type: RuleSetTranslationUserObjectMissingException
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)
Note For more information about the StaticSupport registry subkey, visit the following Microsoft Web site:
Hotfix informationA 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:
PrerequisitesYou must have BizTalk Server 2006 R2 and BizTalk Accelerator for Swift 3.0 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe 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.
Collapse this tableExpand this table
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 meTo run this workaround automatically, click the Fix this problem link. Then click Run in the File Download dialog box, and follow the steps in this wizard.
Fix this problem
Microsoft Fix it 50055
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.
Now go to the "Did this fix the problem?" section.
Let me fix it myselfImportant 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:
322756To work around this problem, disable the StaticSupport registry subkey. To do this, follow these steps:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Did this fix the problem?Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support
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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 950536 - Last Review: October 9, 2011 - Revision: 4.0