BizTalk Server 2013 R2 BHM toolBizTalk 2013 R2 ships with a new tool called as “BizTalk Health Monitor”. BHM is freely available for all BizTalk 2013 R2 users. More about BHM tool at BizTalkHealthMonitor
These are the few recent issues that I have faced with BtsNTSvc.exe.
1. BtsNtSvc.exe crashes
BizTalk Server 2010 btsntsvc.exe crashed with the error
Application: BTSNTSvc64.exeFramework Version: v4.0.30319Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF539C059 (000007FEF5030000) with exit code 80131544
After some analysis I found that the process was crashing because of a 4.5 framework component. Uninstalled framework 4.5 and installed 4.0 post which the issue was resolved.
Since BizTalk 2010 is not tested with framework 4.5, it can cause unexpected behavior like this.
2. No BizTalk assembly got loaded to BTS 2010 process.
All my BizTalk process failed with the error “Could not load file or assembly ‘xxxx' or one of its dependencies”. This was very strange, as no assembly was loaded from the GAC. But all the assemblies were present in assembly 4.0 folder.
After taking procmon, I found that the bts process was looking for assemblies in assembly 2.0 folder instead of assembly 4.0 folder. More details on GAC 4.0 can be found on this link. This was because the config entry <supportedRuntime version="v4.0" /> which directs BizTalk process to point to 4.0 assembly was missing in the btsntsvc.exe.config file.
This key is present by default in config file, these default keys should not be removed.
3. COM Exception
There is another key in btsntsvc.exe.config file which helps in calling the com components from .NET 4.0 framework onwards. Detailed description has been posted in this link.
Written byShashidharan Krishnan
Reviewed by Jainath Ramanathan
Microsoft India GTSC