Possible Issues With BizTalk Host

0

In our BizTalk environment, we have specific hosts for processing, receiving and sending. A few days ago, we saw the following information message in the event log.

The following BizTalk host instance has initialized successfully. 

BizTalk host name: SendHost
Windows service name: BTSSvc$SendHost 

This message started happening at 1:04:41 AM and shows up about every minute until 10:01:05 PM that night. It also appears that each time the host as initialized, everything that would have been queued to send would start sending. So each minute, the same data appears to attempt to send - as there is nearly an equal number of Error messages in the Event Log for all our various interfaces.

I'm wondering what would cause the Send Host to reinitialize itself every minute, and if it happens again, how to find out what's causing it. Has anyone seen this type of behavior before? If so, how did you resolve it?

** EDIT **

At 1:00:24 AM, the following error was logged in the Application Log

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 System.Runtime.AsyncResult.Complete(Boolean)
   at System.Runtime.AsyncResult.Complete(Boolean, System.Exception)
   at System.ServiceModel.Channels.ConnectionStream+IOAsyncResult.OnAsyncIOComplete(System.Object)
   at System.ServiceModel.Channels.SocketConnection.FinishRead()
   at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(System.Object, System.Net.Sockets.SocketAsyncEventArgs)
   at System.ServiceModel.Channels.SocketConnection.OnReceiveAsyncCompleted(System.Object, System.Net.Sockets.SocketAsyncEventArgs)
   at System.Net.Sockets.SocketAsyncEventArgs.OnCompleted(System.Net.Sockets.SocketAsyncEventArgs)
   at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationSuccess(System.Net.Sockets.SocketError, Int32, System.Net.Sockets.SocketFlags)
   at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

And then at 1:00:24 AM the following error is logged

Faulting application name: BTSNTSvc.exe, version: 3.11.158.0, time stamp: 0x538aea40
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d2be6
Exception code: 0xe0434352
Fault offset: 0x00010f22
Faulting process id: 0x1f0c
Faulting application start time: 0x01d0603d63ff5bbe
Faulting application path: C:\Program Files (x86)\Microsoft BizTalk Server 2013\BTSNTSvc.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: fd2a4f01-d2c4-11e4-9411-005056b5474a
Faulting package full name: 
Faulting package-relative application ID: 

Then at 1:03:39 AM the following Information event was logged:

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\svc_BTSHost\AppData\Local\Temp\WER5EA7.tmp.appcompat.txt
C:\Users\svc_BTSHost\AppData\Local\Temp\WERA73C.tmp.WERInternalMetadata.xml
C:\Users\svc_BTSHost\AppData\Local\Temp\WERA75C.tmp.hdmp
C:\Users\svc_BTSHost\AppData\Local\Temp\WER3885.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue   \AppCrash_btsntsvc.exe_8592b3518472b55b77d4f91bb554882409312a0_cab_3c0d3d42

Analysis symbol: 
Rechecking for solution: 0
Report Id: fd2a4f01-d2c4-11e4-9411-005056b5474a
Report Status: 4

The next event logged was at 1:04:41 AM - the Host initializing successfully.

The above two error events and information event occur just before the SendHost is initialized event for the next 21 hours

biztalk
biztalk-2013r2
asked on Stack Overflow Apr 9, 2015 by djm61 • edited Apr 10, 2015 by djm61

2 Answers

1

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. It also seems like it's a bug in the adapter.

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

answered on Stack Overflow Apr 10, 2015 by Dan Field • edited Apr 28, 2015 by Dijkgraaf
1

It is a bug agreed by microsoft and given fix in CU5 but though it is installed still issue comes.My Finding is by default HTTP adapter timeout is set to 0, after increasing the timeout duration issue got resolved.

answered on Stack Overflow Dec 23, 2016 by Sathish Manokar

User contributions licensed under CC BY-SA 3.0