SSO Application configuration requires to reduce burden on BizTalk Configuration file, because using BizTalk configuration file some time create problem if any one by mistake update some invalid data then it will not run any BizTalk application. Also, you cannot set up value from BTSConfig in custom pipeline. So, to overcome this issue, there is … Continue reading SSO Application configuration
Issue: Webhost failed to process a request. Sender Information: System.ServiceModel.Activation.HostedHttpRequestAsyncResult/33808916 Exception: System.ServiceModel.ServiceActivationException: The service ServiceName.svc cannot be activated due to an exception during compilation. The exception message is: Receive location for address ServiceName.svc not found. (The BizTalk receive location may be disabled.). ---> Microsoft.BizTalk.Adapter.Wcf.AdapterException: Receive location for address ServiceName.svc not found. (The BizTalk receive location … Continue reading Microsoft.BizTalk.Adapter.Wcf.AdapterException: Receive location for address ServiceName.svc not found
Issue: XML is missing in XMLDisassenbler stage: There was a failure executing the receive pipeline: Source: "XML disassembler" Receive Port URI Reason: Item has already been added. Key in dictionary: 'Request' Key being added: 'Request' Resolution: When we use ESB pipeline in BizTalk Receive location, this will happen when there is multiple schema in BizTalk … Continue reading XML is missing in XMLDisassenbler stage: There was a failure executing the receive pipeline: Source: XML disassembler
This blog is to explain how to handle below requirements in BizTalk Receive Pipeline. Handle Non-List/Array json messages Handle List/Array json messages Remove special characters before Json Decoder pipeline stage Let's discuss these points. Handle Non-List/Array json messages By default, BizTalk Receive Pipeline Json Decoder can convert the Json message to Xml message. Example: { … Continue reading Handle Array/List Json messages in BizTalk Receive Pipeline
Issues: The type or namespace name does not exist in the namespace in orchestration. Reason: When we have start building solution and add orchestration. And after some time we change the name or design of the solution. And then if we create a new orchestration, that orchestration would have different namespace from older solution because solution … Continue reading The type or namespace name does not exist in the namespace.
It was amazing to get this issue. Today morning I opened my BizTalk admin console and got this issue. I don’t know what was happened. Yesterday It was working fine and perfectly. An Internal Failure occurs for unknown reason (WinMgmt) I have got some weird reason for this. My machine has run window updates and … Continue reading An Internal Failure occurs for unknown reason
This blog is to explain how to call C# components from BizTalk. I am going to explain this scenario by taking simple example like Addition of two number in C# component and call the C# method from BizTalk Orchestration. First, we need to create a C# class library by following below steps. Start-->VisualStudio-->Click on Visual … Continue reading Calling a .net component from BizTalk orchestration
Property Promotion: Property Promotion in BizTalk is usually about taking values from incoming message and moving them into the context of the message, so they are easily accessible and usable for routing. The context of message is a set of metadata about a message that resides in the message box with the message, allowing different … Continue reading BizTalk Property Promotion
