As a BizTalk consultant, it is always important to know the product and its features inside out. Knowing the cards you have to play with when designing a solution, gives you an advantage as you know what you can expect in certain situations.
The WCF-SQL adapter is certainly one of the better known adapters out there, so why decide to write yet another piece on it? There are already plenty of blog posts out there, yet I often find myself double-checking certain behaviors and I wanted to write something so I could refer to it at a later stage and help some people out less experienced.
I know there already is an excellent article up on TechNet around this topic, called Typed Polling with WCF-SQL Adapter: Best Practices and Troubleshooting Tips, but the article here will try to add some extra to that.
Recently I had a project where I needed to use the Microsoft Office Excel BAM add-in. At Codit Belgium, where I work, we have an Office 365 subscription.
I followed the guide Enabling BAM Add-In for Excel 2016, by Sandro Perreira, but was unable to find the BAM Add-in within my Excel installation.
With the latest CU’s for BizTalk Server, the Purge and Archive job can now be configured to clean up orphaned instances. The biggest advantage is that the cleanup is done without any downtime…. yes this means you no longer need to run the BizTalk Health Monitor to clean them up!
The change was marked in the following Microsoft Support article: Orphaned BizTalk DTA service instances are not removed by the “DTA Purge and Archive” job in BizTalk Server
Every now and then, when dealing with BizTalk orchestrations, you might encounter issues you can’t explain. Things like the following, infamous error, may occur without any valid reason:
#error: Errors exist for one or more children
Even after fixing every error, you rebuild the project and/or solution, and the error is still not fixed…
You may know the issue when opening a BizTalk orchestration and it opens like this:
Note: I blurred the code to protect the name of my client.
Not much you can do about it, except right-clicking the orchestration and clicking ‘Open With…’ and choosing the BizTalk Orchestration Designer.
However, if you close the BizTalk Orchestration Designer again, and double-click the odx file, it once again opens in the first, yet useless, view.
(This blog post was co-written by Pieter Vandenheede & Glenn Colpaert, both colleagues at Codit)
We finally admit it… we both were the brains behind the CrazyBizTalk account. There… it’s in the open. After Integrate 2017, day 3, we were no longer able to keep it a secret, so there is no use of denying it anymore…
It was a fun ride, which started in 2013 already. We’ve written this post to give you some insights on how it all got started, the fun we had through the years and what the next steps are.
At Codit, I manage the blog. We have some very passionate people on board who like to invest their time to get to the bottom of things and – also very important – share it with the world!
That small part of my job means I get to review blog posts before publishing on a technical level. It’s always good to have one extra pair of eyes reading the post before publishing it to the public, so this definitely pays off!
An even smaller part of publishing blog posts is making sure they get enough coverage. Sharing them on Twitter, LinkedIn or even Facebook is part of the job for our devoted marketing department! And analytics around these shares on social media definitely come in handy! For that specific reason we use Bitly to shorten our URLs.
Every time a blog post gets published, someone needed to add them manually to out Bitly account and send out an e-mail. This takes a small amount of time, but as you can imagine it accumulates quickly with the amount of posts we generate lately!