There are simple BizTalk Server installations and then there are some quite annoying BizTalk Server topologies and complex configurations which tend to give
There is something special when you find a solution or possible solution to an annoying error message (for not using another type of language) and this is one
Happy to introduce my first guest blog author: Peter Vervoorn from Virtual Green Peter is a very experienced integration specialist He has been working in ICT
BizTalk Server WCF-SAP Adapter: System.ArgumentException: An item with the same key has already b...
Following my last post and continuing on the pain points of BizTalk Server infrastructure tasks migration, I end up founding another interesting error:
BizTalk Server WCF-SAP Adapter: SAP.Middleware.Connector.RfcCommunicationException: LOCATION CPIC...
I’m currently migrating a BizTalk Server infrastructure from BizTalk Server 2013 R2 to BizTalk Server 2016, this is a simple task to do in terms of BizTalk
BizTalk Custom Functoid: Extension function parameters or return values which have Clr type Char ...
Back to Errors and Warnings, Causes and solutions, this time with a surprising error that I got while I was testing a custom Functoid that I had developer:
BizTalk Assessment: PowerShell to check what BizTalk Server 2016 Feature Packs are installed in y...
In the past, I release this PowerShell in order that any BizTalk Administrator to check and control which BizTalk Server Feature Pack was installed in your
After a tweet exchange with Mark Brimble a fellow “BizTalker” that I respect and admire, I realized that I had developed a PowerShell script some time ago
I love this project! I have much fun doing it, and I use it a lot in my clients So for me is what I call a win-win situation So today I update BizTalk Mapper
And once again I decide to publish another release on my Mapper Extensions UtilityPack project adding new functionalities to this toolset This time I decided