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 2020 CU 3 is now available at, KB5007969 – Cumulative Update 3 for Microsoft BizTalk Server 2020
Fixes for adapters include
Improvements
On the blog post that announced it, they also say
As a quick reminder, for BizTalk Developer Tools please also update/install version 3.13.2.0 of the BizTalk Server Visual Studio extension in addition to installing the CU package. The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or from within Visual Studio – Manage Extensions. Please note that we have not updated the extension since CU1 so you can skip this step if you have already installed it previously.
Something non BizTalk for once.
I needed to move my MFA in Microsoft Authenticator to a new phone and I went from a Android to an iPhone, for which the restore from backup won’t work. For most of my accounts it was relatively straight forward, I would launch a private window and go to http://aka.ms/mfasetup, log in with the credentials, authenticate on the old phone, and then just add the authentication on the new phone via Add Method.
However there were some guest accounts in the form of MYNAME_COMPANYDOMAIN#EXT#clienttenancy.onmicrosoft.com which were more of a problem. It took a while to find an post on the internet with a solution, but it was a post in this thread that solved it for me.
What you have to do is go to myapps.microsoft.com/resourcetenant.onmicrosoft.com, replacing resourcetenant with your clients Azure/DevOps tenancy, and log in with your company credentials.
Then go to your profile, Security Information, Add new method, and enrol your new phone. After testing it you can delete your old phone there and delete it out of your the Microsoft Authenticator App on your old phone
Microsoft have released CU9 for BizTalk 2016 in August, KB5005479
Three fixes for Adapters
One fix for Admin tools
And an Updated external dependencies, WinSCP to 5.19.2, so if you use SFTP make sure you install that.
BizTalk Server 2016 Feature Update 3 with CU9 is available here
IMPORTANT: You should not install a CU, if you have a feature pack installed, see BizTalk 2016 Feature Pack vs BizTalk 2016 CUs
Microsoft have announced that .Net 4.5, 4.6 and 4.6.1 are going to be end of life by April 26, 2022.
So as per my blog BizTalk supported Microsoft .Net Frameworks that is going to mean that BizTalk 2013 which can only run on .Net 4.5 that will no longer be getting patches. So if you haven’t been thinking about upgrading BizTalk, now is probably time to start thinking about that.
BizTalk 2013 R2 can run on .Net is 4.6, so make sure you have installed .Net 4.6.2
If you are running BizTalk 2016 with .Net 4.6 you will want to make sure you are at 4.6.2 or either go to .Net 4.7.2 (with at least CU2), or .Net 4.8 (with CU7 and above).
BizTalk 2020 will be running on 4.7.2, but I’m sure Microsoft will support .Net 4.8 for that soon as well.
As a side note, Microsoft is also retiring any contents signed with SHA-1 as per .NET Framework retiring SHA-1 content and UPDATE: SHA-1 signed content to be retired
After changing a SAS key on the Azure Service Bus and updating the SAS credentials in the web.config for all the receive locations, I encountered some errors to do with one of the RelayEndpoint receive locations.
The Messaging Engine failed to retrieve the configuration from the database. Details:”80131014″.
And
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/52231697
Exception: System.ServiceModel.ServiceActivationException: The service ‘/Company.BT.DocMan.SharePoint/sync/Document/v1/Document.svc’ cannot be activated due to an exception during compilation. The exception message is: Receive location for address “/Company.BT.DocMan.SharePoint/sync/Document/v1/Document.svc” not found. (The BizTalk receive location may be disabled.). —> Microsoft.BizTalk.Adapter.Wcf.AdapterException: Receive location for address “/Company.BT.DocMan.SharePoint/sync/Document/v1/Document.svc” not found. (The BizTalk receive location may be disabled.)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.ReceiveLocationManager2.GetEndpointContext(Uri uri) at Microsoft.BizTalk.Adapter.Wcf.Runtime.WebServiceHostFactory3.CreateServiceHost(String constructorString, Uri[] baseAddresses)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
— End of inner exception stack trace —
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
Process Name: w3wp
Process ID: 2496
Browsing to the receive location URL also resulted in the error that the receive location may be disabled.
The solution, recycle the App Pool that the web service was under in IIS.
As per the announcement by Microsoft BizTalk Server 2020 CU2 is available for download.
For the adapters, SFTP gets 4 fixes, the SB-Messaging adapters 3 fixes, the SAP adapter two fixes and one fix each for the WCF-SQL, Logic App adapters.
Also included is a fix to address configuring log shipping, and also a fix that prevented host instances and admin console not starting if the default web proxy is disabled, a fix for a receive location polling outside the service window and an Arithmetic overflow with convoy messages. Import/export of send handler will now include the configured send handler. And a fix for a null reference error when searching in Archived DTA DB.
Also three fixes for development either not surfacing errors or becoming non-responsive. As per the announcement you need to update your extension if you haven’t already done so.
As a quick reminder, for BizTalk Developer Tools please also update/install version 3.13.2.0 of the BizTalk Server Visual Studio extension in addition to installing the CU package. The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or from within Visual Studio – Manage Extensions. Please note that we have not updated the extension since CU1 so you can skip this step if you have already installed it previously.”
Despite earlier indicating that they weren’t going to release updated Feature Updates with new CUs, Microsoft have actually released Microsoft BizTalk Server 2016 Feature Update 3 with CU8. So you can still get all those CU8 fixes if you have feature packs installed, as you should not install a CU only, if you have a feature pack installed, see BizTalk 2016 Feature Pack vs BizTalk 2016 CUs
Note: Microsoft have release CU 8 for BizTalk 2016 Feature Pack CU 8 can be found here, you should not install a CU only, if you have a feature pack installed, see BizTalk 2016 Feature Pack vs BizTalk 2016 CUs
This CU contains fixes for following fixes for Adapters
There the two remaining fixes are for BizTalk Server Setup and Configuration “Cannot insert duplicate key row in object ‘dbo.bts_LogShippingHistory’ with unique index” error while configuring log shipping destination
And BizTalk Server Accelerators Digest is not injected in the ACK in FileAct SnF PUSH mode when signature and non-repudiation are requested
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