Below a list of know bugs, issues, & other quirks* of BizTalk 2013 R2 (mainly CU3) and Visual Studio 2013 (update 4) , but I will update with fixes as the CUs come out or when I know about a new issue, so if you have another one I will add it (and link to it if you have a blog about it) if you let me know. This in addition to the ones listed by Microsoft on Known Issues in Installation, Configuration, and Deployment
* My definitions for classifying these are Bug: Causes negative impact and no known work around or requires a lot of effort to work around. Issue: Causes negative impact but has an easy or quick work around. Missing: A feature that BizTalk doesn’t have that would make our life easier. Quirk: Something strange or unusual but does not cause a negative impact so far as known.
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.
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″.
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.
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 184.108.40.206 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.”
The new “Error Threshold” property disables the receive location on error. The receive location is disabled when the error threshold is exceeded. If the error threshold is set to 0, then the receive location is not disabled.
The exceptions that occur in the SFTP receive location is written to the event log. This helps you troubleshoot any issues that affect the receive location.
I had a test environment where the SQL Agent job MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb had been failing for a while. This job runs exec bts_CleanupDeadProcesses in the message box DB. It was failing with the error
Executed as user: Domain\Account. Could not find stored procedure ‘dbo.int_ProcessCleanup_OLDHOSTNAME’. [SQLSTATE 42000] (Error 2812). The step failed.
Now the clue in this was that the stored procedure was trying to execute another stored procedure with a name of an a host that had been decommissioned, along with several others, after there had been some issues with them and replacement host and host instances had been created.
In that stored procedure it had this
DECLARE btsProcessCurse CURSOR FAST_FORWARD FOR
SELECT s.uidProcessID, s.nvcApplicationName FROM dbo.ProcessHeartbeats AS s WITH (ROWLOCK READPAST)
WHERE (s.dtNextHeartbeatTime < @dtCurrentTime) OPTION(KEEPFIXED PLAN)
So to see what that was getting I ran the below
declare @dtCurrentTime datetime
set @dtCurrentTime = GetUTCDate()
FROM dbo.ProcessHeartbeats WITH (ROWLOCK READPAST)
WHERE (dtNextHeartbeatTime < @dtCurrentTime) OPTION(KEEPFIXED PLAN)
This gave a list of very old heartbeats for all the old host names. To resolve the issue I changed the select * into a delete, and ran that, and the SQL Agent Job is now running correctly.
There is an an post asking for Feedback on the new Microsoft forums techcommunity that is talking about a CU8 for BizTalk 2016. However it indicates that they are considering releasing only for the base RTM and not for those with Feature Packs, and those that have feature packs are expected to upgrade to BizTalk 2020
Feature Updates to BizTalk Server 2016 provided early production ready access to BizTalk Server 2020 features. All those features are rolled up and now available with BizTalk Server 2020 release. We believe that Feature Updates to 2016 have served its purpose by providing early access to capabilities under work for 2020. 2020 release has further enhanced those features due to the freedom to make larger code changes in new release. BizTalk Server 2020 release has been available since the beginning of year and we released CU1 recently.
Feature Updates were available for select BizTalk Server customers strictly on an opt-in basis with an understanding that these customers will move to 2020 release soon after its availability. BizTalk Server Enterprise customers with Enterprise Agreement are eligible for free upgrade to BizTalk Server 2020. BizTalk Server 2020 supports in-place and seamless upgrade from BizTalk Server 2016.
We are in the planning process for CU8 release of BizTalk Server 2016 and were hoping, keeping above in mind, to continue releasing the CUs for the base 2016 (aka RTM) versions that caters to all SKUs and customers uniformly. Those who were on accelerated cadence by opting into Feature Packs, will move to BizTalk Server 2020 for their support requirements
We want to gather community response before finalizing our decision. Let us please use the discussion space under this post with constructive comments to help us arrive at a decision that helps us optimize engineering resources without compromising the customer needs.
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.
Recommendations for SFTP Receive Locations
Have a dedicated host for receive locations using SFTP
Increase the Maximum Worker threads setting to 500 on that host instance
Check how frequently you poll (the default is 5 seconds)
Put a schedule on to only poll during the periods you need.
Disable message body tracking if it is not needed.