Symptoms
Assume that you have installed the .NET Framework 4.5.x on a server that has Microsoft BizTalk Server 2010 or 2013 installed. After this, the BizTalk Host instances crash with error code 80131544 that resembles the following in the event log:
Log Name: ApplicationSource: .NET RuntimeDate: Event ID: 1023Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: <ServerName>Description:Application: BTSNTSvc64.exeFramework Version: v4.0.30319Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FDED170BC1 (000007FDECE00000) with exit code 80131544.Log Name: ApplicationSource: Application ErrorDate: Event ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: <ServerName>Description:Faulting application name: BTSNTSvc64.exe, version: 3.10.229.0, time stamp: 0x50fe567aFaulting module name: clr.dll, version: 4.0.30319.19106, time stamp: 0x51a512d4Exception code: 0x80131544Fault offset: 0x0000000000370bc1Faulting process id: 0xca8Faulting application start time: 0x01ceb6394f1dd32aFaulting application path: <Disk Name>:\Program Files (x86)\Microsoft BizTalk Server 2013\BTSNTSvc64.exeFaulting module path: <Disk Name>:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dllReport Id: <ReportId>Faulting package full name: Faulting package-relative application ID: Log Name: SystemSource: Service Control ManagerDate: Event ID: 7031Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: <ServerName>Description:The BizTalk Service BizTalk Group : BTSOrchHost service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Cause
This issue occurs because you install the .NET Framework 4.5 in your BizTalk Server environment, and it is not officially supported prior to Cumulative Update 7 (CU7) for BizTalk Server 2010. You have to use the .NET Framework 4.0 when you run BizTalk Server 2010 Cumulative Update 6 (CU6) or earlier.
Resolution
Cumulative update information
This issue was first fixed in the following cumulative update of BizTalk Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around the issue, turn off XLANG AppDomain Shutdown by following steps:
-
Locate to your BizTalk Server folder. By default, it is C:\Program Files (x86)\Microsoft BizTalk Server 2013.
-
Save a copy of the BTSNTSvc64.exe.config file by using a new name.Note Save a copy of the BTSNTSvc.exe.config file if it is a 32-bit host. You can check the error message to see whether the crash occurs to BTSNTSvc.exe or BTSNTSvc64.exe.
-
Open the original file in notepad and locate the <configuration> node. Then, directly below it, add the following:<configSections><section name="xlangs" type="Microsoft.XLANGs.BizTalk.CrossProcess.XmlSerializationConfigurationSectionHandler, Microsoft.XLANGs.BizTalk.CrossProcess" /></configSections>
-
Locate to the </runtime> node, and add the following:<xlangs><Configuration><AppDomains AssembliesPerDomain="50"><DefaultSpec SecondsIdleBeforeShutdown="-1" SecondsEmptyBeforeShutdown="-1"/></AppDomains></Configuration></xlangs>
-
Recycle the host.
More Information
Starting with CU7, BizTalk Server 2010 supports both .NET Framework 4.0 and 4.5.x for the runtime. CU7 can be installed either prior to or after you install the .NET Framework 4.5.x.
