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.
Note: It has been reported on Twitter that “We have some issues with the new #biztalk CU7. The json encoder has started formatting boolean values as string values, like “true” instead of true.” and “As we wanted the FTP fixes in CU7 we installed it anyway and replaced the jsonextension dll with an older version.”
In that same thread “Little warning, rolling back CU7, does not rollback the jsonextension version.”
After 6 month of total radio silence concerning the next release of Microsoft BizTalk Server (being announced in June of 2019 at Integrate London), I suddenly learned that the next version (BizTalk Server 2020) had been released on January 15th 2020.
Having waited a long time for this day, primarily because of the platform lift (the use of Visual Studio 2019, Windows Server 2019 and SQL Server 2019) and getting all of the previous Feature Pack features from BizTalk 2016 into the Standard Edition (most of my customers do not use Enterprise edition), I created an Azure Virtual Machine with a pre-installed Windows Server 2019 and SQL Server 2019, and sat out to get the new BizTalk Server up and running.
The following is a short walk through of what I did and some of my findings.
Up till, and including, BizTalk Server 2016, the SFTP adapter included with BizTalk Server, has only supported SSH server host key fingerprints using the RSA algorithm, also called an RSA key fingerprint. Previously, you could connect to an SFTP server using FileZilla, and get the RSA key fingerprint that way. In recent versions, FileZilla will […]
Sometimes when you are connecting to an API you get errors similar to the below
System.TimeoutException: The HTTP request to ‘https://XXX.my.salesforce.com/services/apexrest/xxxxxx’ has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. —> System.Net.WebException: The request was aborted: The request was canceled. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result) — End of inner exception stack trace — Server stack trace: at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result) Exception rethrown at : at System.Runtime.
System.ServiceModel.CommunicationException: An error (The request was aborted: The request was canceled.) occurred while transmitting data over the HTTP channel. —> System.Net.WebException: The request was aborted: The request was canceled. at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context) at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStreamAsyncResult.CompleteGetRequestStream(IAsyncResult result) — End of inner exception stack trace — Server stack trace: at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object outs, IAsyncResult result) at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result) Exception rethrown at : at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IM
This can be because using the default number of maximum connections of 2 and there too many messages queuing up to be processed in a timely manner. You can adjust this by adding the below to your BTSNTSvc.exe.config and BTSNTSvc64.exe.config, setting a default maximum connection and some specific connections for APIs where you either have a higher or lower limit.
Note: This I believe limit is Per Host Instance, so you either need to ensure that all send ports to an address are on the same Host Instance, or you need to divide the maximum number of allowed connections by the number of Host Instances that go to that address.