when you have escape characters in the string the liquid template fails

I came across a scenario, where I got bad request error when I have double quotes(“) in my incoming string property while performing json to json transforming using liquid template. When there is not double quotes it works as expected.   My Liquid Template: performing a simple append of first name and last name {    “fullName”:… Read more

Logic apps Service bus connector not honoring Maximum message count

You might come across a scenario where you dont receive the batch of messages configured under maximum message count property in your logic app service bus connector setting. In this example, i have configured the maximum message count as 20 but still I recieved only 1 or 2 messages every time even when i had… Read more

Original Run Vs Resubmitted Run in Logic apps

In Logic app, you would often come across a scenario to differentiate between the original run and if the run is resubmitted via the Logic app portal(or Rest API) the Resubmitted Runs reuse Client Tracking ID of the Original Run, so they can be correlated. So IF RUNID= ClientTrackingID THEN Original RUN IF RUNID ≠… Read more

Logic App: Json serialization issue when receiving message from Service Bus

When parsing message received by logic App from Service, got the error “ InvalidJSON. The ‘content’ property of actions of type ‘ParseJson’ must be valid JSON. The provided value ‘@string3http://schemas.microsoft.com/2003/10/Serialization/�>{ “Field1”: “Test1”, “Field2”: “Test2”, “Field3”: “Test3″ }’ cannot be parsed: ‘Unexpected character encountered while parsing value: @. Path ”, line 0, position 0.’.” We have the… Read more

“MMC could not create the snap in” error for Biztalk Admin console

After in place upgrade of operating system on BizTalk Server, when i launch BizTalk admin console we got the error “MMC count not create the snap in”   Resolution:  Repair BizTalk Server from Add/Remove programs… Read more

MQSC related host instance fails after BizTalk Server restart

After restarting Biztalk Server, Host instances running MQSC adapter fails to start and the error message in the event viewer is “Could not load file or assembly ‘Microsoft.BizTalk.Adapter.Mqsc.ImqWrapper.dll’ or one of its dependencies. The network path was not found. A dependency could not be found. Refer to product documentation for information on MQSC Adapter software… Read more

xml resultset from SQL store procedure is splitt into multiple nodes in Logic Apps

I have a stored procedure which returns an XML  result set. when I execute the stored procedure, the output is a single XML as below. CREATE PROCEDURE [dbo].[TESTSP] AS BEGIN SELECT * from testtable FOR XML AUTO END   The output is a single xml object as below. <testtable ID=”1″ Detail=”testdata  ” /><testtable ID=”1″ Detail=”testdata … Read more

Orchestration Subscription Throttling

One of the less heard features of orchestration throttling is Subscription Throttling.  The Subscription based throttling will decide when to pause/resume the messages from moving to Subscribing orchestration instance based on the number waiting to be consumed. Recently I came across a scenario, where we had to utilize this functionality, but we don’t have a… Read more

Logic Apps : Blob name is null or empty

Recently when working with Azure blob Storage Action :  Extract Archive to Folder I faced the error “Blob name is null or empty”. Host { “api”: { “runtimeUrl”: “https://logic-apis-westeurope.azure-apim.net/apim/azureblob” },     Method : post Path : /datasets/default/extractFolderV2 Queries: { “destination“: “/testoutput“, “source“: “/test/shashiwebsite_201506011619.zip” } Output Body : { “status”: 400, “message”: “Blob name is… Read more

BizTalk Receive Location crashes with the error “80131522”

When enabling BizTalk Receive location getting the error “Event Type:Error Event Source:BizTalk Server 2006 Event Category:BizTalk Server 2006 Event ID: 5644 Computer: xyz Description: TheMessaging Engine failed to add a receive location “rloc_abc” with URL“C:\Test\In\*.*” to the adapter “FILE”. Reason: “80131522” Taking a process dump from the procdump, in the cmd promptwe get the error… Read more