HI All

Our Biztalk 2013 R2 host instance getting restarted at regular intervals. Please find the below logs and advice.We get three type of errors in the event viewer . Please advice

---------------------------- Windows Error Reporting----------------------------------------

Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: BTSNTSvc.exe
P2: 3.11.158.0
P3: 538aea40
P4: System.ServiceModel
P5: 4.0.30319.34230
P6: 53be5c02
P7: c6
P8: 152
P9: I0SHPZEWVQV4P1UJY40X15MQTHF34RR5
P10:

Attached files:
C:\Users\SASITBTSInstAcc\AppData\Local\Temp\WERED37.tmp.appcompat.txt
C:\Users\SASITBTSInstAcc\AppData\Local\Temp\WEREDB5.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_BTSNTSvc.exe_a14a634660c9dfdd5e8e042f027999735366e6_00000000_cab_1398edf2\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_BTSNTSvc.exe_a14a634660c9dfdd5e8e042f027999735366e6_00000000_cab_1398edf2\minidump.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_BTSNTSvc.exe_a14a634660c9dfdd5e8e042f027999735366e6_00000000_cab_1398edf2

Analysis symbol:
Rechecking for solution: 0
Report Id: 40f4fd3e-ff8f-11e4-80d0-000c29a69f2a
Report Status: 4
Hashed bucket:

-------------------------------------Application Error -----------------------------

Faulting application name: BTSNTSvc.exe, version: 3.11.158.0, time stamp: 0x538aea40
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54504ade
Exception code: 0xe0434352
Fault offset: 0x00014598
Faulting process id: 0x1d24
Faulting application start time: 0x01d0939c00cea40c
Faulting application path: C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\BTSNTSvc.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 40f4fd3e-ff8f-11e4-80d0-000c29a69f2a
Faulting package full name:
Faulting package-relative application ID:

---------------------------------------- .Net Runtime---------------------------------------------

Application: BTSNTSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.CallbackException

Stack:
   at Microsoft.ServiceModel.Channels.Common.Design.AdapterAsyncResult.SignalFinished(System.Object, System.Exception)   at Microsoft.ServiceModel.Channels.Common.Channels.AdapterRequestChannel.AsyncCall(System.Object)   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

While not specific things you should check (3 and 4 are what I'm inclined towards).

1. OS Version is supported for BizTalk Server 2013 R2 ?
2. OS version patched to the latest set
3. .Net Framework patched to the latest version.
4. While .Net 4.0 is supported.. do you have 4.5 installed with latest patches?

This apart, you should log a call with Microsoft.

Regards.

Shank - We get teh error when we try send a request using  WCF-SQL Adapter.

When we stop the Application we dont see to get that error.

Regards

Suresh

Your host instance is crashing due to an unhandled exception occurring in the adapter you're using. This is very likely due to some configuration error in your adapter, or response from the server that BizTalk isn't expecting.

See BizTalk 2013 R2 - WC-Custom Adapter SAP-Binding: Unhandeld (sic) exception on failure tests for someone having similar issues with sapBinding.

This seems to be a known issue of host crashing, request you to open a ticket with Microsoft Support (http://support.microsoft.com) and they should be able to assist you.

Rachit

We have observed similar issue in BizTalk Server 2013 due to idle orchestration and issue was resolved after applying the short term fix suggested here

Note: since you are using BizTalk 2013R2, root cause for your issue may or may not be similar to ours. So be cautious in applying changes to PROD.

HTH !!

I would try to reinstall the WCF Adapter Pack