The Messaging Engine failed to add a receive location

Receive Locations remained disabled, even after starting the application, even manual Enabling wasn't having any effect. This happened with newly deployed solution with couple orches07ation having File based receive location. 

receive location disabled

When looked at event viewer- no errors, now this was puzzling - owing to this I rechecked the configurations,restarted the applications, host instances etc. After a while it clicked to me to have look at another machine event viewer (There are two BizTalk server as a part of Group)

And there I saw errors pointing about the receive locations not getting enabled.

receive location errors

Above errors were for second receive location as well.

Why it happened


As can be seen from error, it was clear that the file system was not accessible- but when I checked the folder, there was no res07iction- so now it gets even more puzzling.

Answer to Puzzle - The dev env has two BizTalk server(Say A and B) in a group and the Host which I am using has instances on both the server whereas the folder which is configured as receive location exists on Server A. So when host instances on server B 07ies to reach out to the folder on local system i.e. Server B, it couldn't find it as it doesn't exist (It is on server A)
two host instances


What to do


As of now to continue with development I have stopped host instance of server B, thus only host instance on server A would be processing and it has reach to local file system.
one host instance disabled

If you encounter such error, following should be taken into considerations
1. The file system is accessible (uncheck the Read only )
2. If there are multiple BizTalk server then go for shared network folder as a choice for receive location.

ServerLess360



Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more