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.
The August 2019 Windows Updates includes .Net 4.8, however most BizTalk versions only support specific version of .Net, and installing a unsupported version of .Net has caused issues in the past. So if you are patching BizTalk servers, make sure to block installing any unsupported .Net Version.
I’m going to start my new adventure as IT blogger with this post about how we can to generate a good documentation of a BizTalk application.Is very common in the day to day find applications without any documentation and if we are talking about BizTalk, even more. BizTalk Documenter is not a new tool, we’ve known […]
Did you ever want to create a list of Send Ports, Receive Locations or Ports? Did you know that rather than manually doing it or writing a PowerShell script, you can just copy from the admin Console and paste it into a spreadsheet?
In the Admin Console, just go to an Application or <All Artifacts> and for example for Send Ports. Press Ctrl+A to select all the ports, press Ctrl+C, switch to a blank sheet in a spreadsheet and press Ctrl+P
This works Orchestrations, Send Port Groups, Send Ports, Receive Ports, Receive Locations, Policies, Schemas, Maps, Pipelines, Resources and even at the higher Applications node.
You can also use it from the query pages from the Group Hub such as Tracked Messages, Instances or Subscriptions or the Context properties of a tracked message.
Would you be negatively impacted if Microsoft Azure stopped accepting all SSLv2, SSLv3, TLS 1.0 and TLS 1.1 connection in the second half of calendar year 2019?
Microsoft is planning the deprecation of TLS 1.0 & 1.1 protocols. To help them understand possible impacts from the deprecation and learn how they can improve your experience, please complete this survey: LINK.
This is a free, event driven by user groups and communities around the world, backed by Microsoft, for anyone who wants to learn more about Microsoft’s integration story. In this full-day boot camp we will deep-dive into Microsoft’s integration stack with hands-on sessions and labs, delivered to you by the experts and community leaders. In this Boot Camp, we will focus on:
Learn how to use event hubs for all your events
Creating Logic Apps using commonly-used connectors
Build reliable and scalable cloud messaging and hybrid integration solutions
Enterprise Integration Pack
Using the Enterprise Integration Pack (EIP) with Logic Apps
How does API management help you organize your APIs and how does it increase security?
Connecting to on-prem resources using the On-Premises Gateway
Hybrid integrations using BizTalk Server and Logic Apps
In all cases this error was resolved by first moving any ports onto another handler and then removing an adapter from a host, restarting the host, testing that the console works and then re-adding them.
In our case we had added two new host instances recently for SFTP adapters to use, both the out of the box Microsoft one and the nSoftware one, and somehow the out of the box one had corrupted some settings on one of the hosts. The trick of course is identifying which adapter, we assumed correctly that it would be the last ones that were changed.
Recently one of the support staff at my company, Daniel Tran, found that one of our clients running a BizTalk 2009 BizTalk server was not processing messages, and errors in the Event log indicated an issue with the SSO database. To resolve this he had to contact Microsoft, and he was advised to follow the steps in the following blog: Continuous Arithmetic Overflow exception with SSO in BizTalk Server.
Essentially a table in the SSO database had reached the maximum int for the primary key in that table. And the solution was to start it back at 1 again. If you are running any older BizTalk environment, it might be an idea to check the SSOX_AuditXPLookup table to ensure that it isn’t coming close to this as well.