Blogging BizTalk

Lets Discuss BizTalk

Tag Archives: BizTalk server

BizTalk 2013 R2 Installation: ESB Tool Kit Installation Error: The network path was not found

While installing the BizTalk 2013 R2 ESB toolkit bumped into the error :
The network path could not be found.

NwPath error

This error should have a corresponding entry in ESB tool kit log. You can find that at the following location ( presuming you are using the default installation path).
C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Bin

You will be able to see the error towards the end of the log. The reason for this error is in the user account being used for configuring the ESB tool kit. The id has to be part of the Administrators. Also if you are using a network domain ID you might see this error. In that case you need to go to the ESB configuration file.

C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Bin\EsbConfigurationTool.exe.Config

Here you will have to modify the various BizTalk groups to the domain groups that you would like to use.
For example:

Change To:

Once done close and reload the ESB configuration tool one more time and reapply the configuration.


Error Message Routing Pattern demo In BizTalk

This topic deals with Error Message Routing Pattern Demo.

Where can you use this? One of the examples may be when your send port end point is erroring out or the subscriber to a RP is unavailable for some reason(For example may be a a send port working in a time window) then you will bump into a scenario where in a message comes in on a receive port and doesn’t finds a subscriber which it would have had it come between the defined time window or  where you may see the Zombie message scenario (Let me accept it is not a very ideal solution to handle the Zombies but may fit your need, one never knows).   It is going to leave you unconsumed messages suspended messages in BizTalk, if you choose to terminate them it can lead to data loss scenario . Even if you resume these messages they going to suspend back because there instance subscription is no longer valid(In case the response was to consumed by orchestration). You may want to handle them and this is one of the way on How can you do it.

I am trying to demo how can handle this.

Lets Create The Non Subscribed Orphaned Message Scenario

1>Create a receive port with the “Enable Routing Failure For Failed Message” ticked in.


2>when you drop a message which has the subscriber defined it will be consumed by the respective BizTalk artifact. Now if you drop a message which has no subscriber defined: You will have a suspended message with no subscriber found error. So you have your orphaned message created at this point in time.
Read more of this post

D Goins Insperience

Technological outformation for this day and age

[INACTIVE BLOG] Connected Thoughts - Thiago Almeida

Connected systems and the occasional picture

Uri Katsir's Blog

BizTalk , BizTalk RFID and .NET


My BizTalk Experiences

BizTalk Server Tutorial

BizTalk Server Concepts and Common Errors

Extremely Talented Monkeys

A Technical Blog by Ed Jones: Azure, .NET, BizTalk, WCF, and SQL Server

On All Things Web

Discussing web development without limits

Vikas Bhardwaj's Blog

All about BizTalk Server, Azure and .NET

Cloud develop

a blog about (cloud) development... because I'm a nerd

Hooking Stuffs Together

My learning logs from day to day work experience about Integration platform using Microsoft technologies.

Connected Pawns

Mainly BizTalk & Little Chess


a blogger in the process.

MS Innovations Blog

Tips, Tricks, and Workarounds for BizTalk and other Microsoft technologies


Katradhu Kaialavu,Kalladhadhu Ulagalavu!

Vijay Microsoft Technical

BizTalk, WCF, ESB ToolKit, Windows Azure

Mind Over Messaging

Musings on BizTalk, Azure, and Enterprise Integration