Featured

BizTalk 2013 R2 known bugs, issues & quirks

I’ve now posted the below article on a TechNet wiki

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.

Continue reading “BizTalk 2013 R2 known bugs, issues & quirks”

BizTalk 2020 – CU1 being planned

If you have some feedback for Microsoft about something you want fixed in BizTalk 2020, here is your chance.

We are actively planning content for CU1 for BizTalk Server 2020. If there is anything you like product group to consider for this, please add to this conversation.

https://techcommunity.microsoft.com/t5/biztalk-server/biztalk-server-2020-cu1/m-p/1220744

Cumulative Update 7 for Microsoft BizTalk Server 2016

CU 7 for BizTalk Server 2016 has been released, and also Microsoft BizTalk Server 2016 Feature Update 3 with CU7

Important: Do not mix installing CU’s and Feature packs.

This CU contains

  • Four fixes/improvements for the SFTP adapter.
  • One fix for the IBM MQ.
  • One improvement for the the MQSeries adapters.
  • One fix for SAP (NCo) adapter.
  • One fix for the HL7 BizTalk Server Accelerators.
  • Five fixes around applying CU’s, Feature Packs and other setup and configuration changes (not counting the SFTP one which I’ve counted under adapters).
  • And a JSON FIX: JSON encoder unable to handle XML schema with the same name for record and one of its elements which is an issue that has caused grief for a few people.

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.”

Also JSON encoder pipeline doesn’t create json array after installing CU7

BizTalk Server 2020 unwrapped

Vertica blog

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.

View original post 859 more words

BizTalk Server 2020 has been released

I can see BizTalk 2020 developer edition available for download today. If you have a Enteprise MSDN account you should be able to see all four versions.

  • Branch
  • Developer
  • Enterprise
  • Standard

Hardware and Software Requirements for BizTalk Server 2020
Surprisingly this says it supports .Net 4.7 rather than 4.8 as was initially announced.

New in BizTalk Server 2020
Mainly what was expected being the features of BizTalk 2016 with Feature Pack 3.

Here are some selected new features of interest

FeatureDescription
Audit LogMaking BizTalk further secure by maintaining audit trails of all management operation.
New Read Only Operator roleBrand new read only operator role to facilitate dev ops model, where access to production stamp is provided without the ability to update anything.
XSLT 3.0New extensible model for runtime map execution, out of box wiring to work with Saxon XSLT3.0.

XSLT Transform Engine
XSLT custom transform implementation
Support for SSO Affiliate applications in SFTP adapter.
Partially disabled receive locations.

The Deprecated & Removed List is also of interest

ProgramStatusReplacement
SamplesRemovedRemoved from BizTalk Server installation.
POP3 and SMTP adaptersDeprecatedOffice 365 adapters
Support for ACS authentication in adaptersRemovedSAS authentication
SOAP adapterDeprecatedWCF-BasicHttp Adapter
Old SQL adapterRemovedWCF-SQL Adapter
BPEL supportDeprecatedNone
JDE OneWorld adapterDeprecatedNone
OWC redistRemovedNone
BAM PortalDeprecatedNone
WCF-NetTcpRelay adapterDeprecatedNone

Finding the SSH server host key fingerprint — BizMunch

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 […]

Finding the SSH server host key fingerprint — BizMunch

Configuring maxconnection in BizTalk

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 [0]:
at System.Runtime.

Or

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 [0]:
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.

<system.net>
       	<connectionManagement>
               	<add address="*" maxconnection="5"/>
                <add address="https://api.limitedconnections.com*" maxconnection="2"/>
                
                <add address="https://api.moreconnections.com*" maxconnection = "10"/>
       	</connectionManagement>
</system.net>

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.

Further reading

HTTP Adapter Configuration and Tuning Parameters
More than 2 Concurrent connections not working in BizTalk 2013
BizTalk MaxConnections
General BizTalk Server Optimizations