Today I was doing some cleanup on a Dev and Test environment with BizTalk Health Monitor, when I noticed the “From latest BHM report”, I’m not sure how long that feature has been there, but it makes it easier to find the Tasks that you need to run.


BizTalk Health Monitor
A about March or earlier, the latest rules for BizTalk Health Monitor started to show the following important warning.
I had already been advising clients to run SFTP receive locations on a separate host instance due to issues where it would silently stop receiving requiring a host instance restart to resolve, possibly related to FIX: SFTP adapter receive locations stop working intermittently during higher load in BizTalk Server
The rule itself also talks about MQSC and DB, but as I didn’t have any receive locations for those it was only warning about SFTP.
I’ve seen that warning even on a BizTalk 2010 environment that has a Custom SFTP adapter installed, possibly because it was also called simply SFTP. However it does not warn about third party SFTP adapters such as the nSoftware one which has a different name.
However, even after changing the Max worker threads to 500 and restarting the Host Instance and re-running BHM, the warning did not go away. Even moving the receive locations running on the nSoftware onto another host instance, and un-configuring the adapter on that host instance didn’t make any difference.
The BizTalk adapter’s default configuration is to poll every 5 seconds. This is rather excessive and should be reduced.
Over a year ago we hit a situation where we got a warning from BHM about .Net 4.6 not being supported, which was a bit of effort to sort out.
Today I looked at the release notes for the latest BizTalk Health Monitor, v4.1 and noticed that in the release notes it said “Removed BizTalk 2013 R2 .NET 4.6.x warning since it is now supported”. I then checked Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2 and sure enough, they have now listed .Net 4.6 as supported for BizTalk 2013 R2.
Here are the other changes for BizTalk Health Monitor
• Fixed issue with losing monitoring configuration
• Upgraded update mechanism to handle all components of BHM
• Added support for displaying each view of a BHM report in HTML format
• Improved update to happen on secondary thread
• Improved the ChkBHMRep.exe tool
• Added support for BizTalk 2013 R2 CU6, BizTalk 2016 CU1, and BizTalk 2016 FP1 (Feature Pack 1)
• Improved report to provide DTA purge job parameters with improved formatting
• Added warning for infinite max SQL memory config
• Fixed some issues with detecting Host Integration Server CUs
• Removed BizTalk 2013 R2 .NET 4.6.x warning since it is now supported
• Updated query and rules repository
We are using BizTalk Health Monitor 3.0 in a clients environments and we get the warning message
Category: Tuning
Caption: ‘maxconnection’ property
Value: Is not present in some BizTalk process config files – You can configure the number of concurrent connections that the SOAP adapter opens for a particular destination server by adding “maxconnection” entry
However I have checked both the BTSNTSvc.exe.config and the BTSNTSvc64.exe.config and the both do have the maxconnection property.
Continue reading “‘maxconnection’ property Is not present in some BizTalk process config files”
A blog about all things testing. Views are my own
Just another Integration blog
Biztalk gotcha!
FURIOUSLY REASONABLE
Technology, music, life, and musings
Spread up technology
Made easy and simple
Blog on BizTalk Server
Stray Notions on All Things Microsoft Azure and BizTalk
Azure, BizTalk, .NET, SSIS, WCF Blogs
Let's learn and share !
Biztalk & Azure Integration Architect : Logic Apps, Serverless, Azure Service Bus, BizTalk Server, and Hybrid Integration
Stories, tips & tricks for BizTalk Server, Azure, Data Science & Machine Learning
Blogging with my head in the (Hybrid) Cloud and my feet on premises! Azure / IoT / Integration
BizTalk blog by Knut Urke
A blog about BizTalk, and other integration tools.
OS Deployment, Virtualization, Microsoft based Infrastructure...
Demystify Integration Development