When integrating with GXS OpenText, I recently encountered an issue with an AS2 setup.
- You receive an inbound message over AS2.
- The AS2 client is setup to receive an asynchronous MDN regardless of the use of a encryption/signing or compression.
- You’ve setup a two-way send port to send out the asynchronous MDN.
- The two-way send port uses AS2Send and AS2Receive pipelines.
With this setup, we encountered the following AS2 error:
An output message of the component “Microsoft.BizTalk.EdiInt.PipelineComponents” in receive pipeline “Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Receive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35” is suspended due to the following error:
An AS2 message was received that did not contain the AS2-From header..
The sequence number of the suspended message is 2.
A couple of months ago Glenn Colpaert & myself, both colleagues at Codit, announced that we both were “the brains” behind the CrazyBizTalk Twitter account.
Since then we’ve been receiving very positive feedback and lots of people have asked us to continue. Although it is tempting to continue with the account, we feel people may become biased by what we think is funny.
However, we also felt that Crazy BizTalk was more than us sending some funny tweets. The account should be opened to a broader public, this to allow people to make fun of their favorite integration topics in an anonymous, but verified and non-toxic way.
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.