Feature blog image

May 19

Warning: BizTalk 2013 R2 is unsupported if you install .Net 4.6

A new critical warning has appeared in the BizTalk Health Monitor for all of our BizTalk 2013 R2 servers after the latest repository update from Microsoft as

By Mark Brimble
Feature blog image

May 1

BizTalk Server 2016 CTP: BizTalk 2013 BAM Alerts configuration error is now fixed.

I was pleased to find that you no longer get an error like “Cannot alter the role ‘NSSubscriberAdmin’, because it does not exist or you do not have

By Mark Brimble
Feature blog image

Mar 29

Azure Service Bus Relays, SAS tokens and BizTalk Server

Many people have written about Azure Service Bus Relays in the past and a summary can be found here Dan Rosanova recently tweeted “We're trying to discourage

By Mark Brimble
Feature blog image

Mar 8

BizTalk Host Settings – “Default application domain for isolated adapter”

What does this setting do In this post I describe why I found this setting useful and ask what are the disadvantages are of turning this setting to

By Mark Brimble
Feature blog image

Jan 4

REST JSON Christmas Puzzle – Work around

I created the following workaround  to my Christmas puzzle I created a custom pipeline that includes the Json encoder and BRE pipeline framework pipeline

By Mark Brimble
Feature blog image

Dec 24

REST JSON Christmas Puzzle

If I use the BizTalk 2013 R2 JSON Encoder pipeline component to convert the following XML <ns0:ASCIISchema

By Mark Brimble
Feature blog image

Dec 11

Authenticating Salesforce REST API calls to custom Apex endpoints

Seroter has shown us how to call the Forcecom REST API from BizTalk Server and we used this to successfully call standard Forcecom objects like

By Mark Brimble
Feature blog image

Nov 29

BizTalk 2013 R2 JSON Encoder error – “Object reference not set to an instance of an o...

In a previous post I lamented that the JSON encoder pipeline component throws an error if a soap fault is sent to it My colleague Deepa Kamalanthan has

By Mark Brimble

Nov 26

BizTalk 2013 R2 JSON Encoder error – “Object reference not set to an instance of an o...

We have discovered that if a SOAP fault is sent to a pipeline using the JSON Encoder the following error occurs; A response message sent to adapter

By Mark Brimble
Feature blog image

Sep 25

Using BizTalk 2013 R2 to transform an XML message element to a JSON array

I wanted to know whether the out of the box  JSON encoder pipeline component creates an JSON array  if there is only one repeating XML fragment One of my

By Mark Brimble
turbo360

Back to Top