Prerequisites:

The following solution should be built on a development machine with: 

a) Visual Studio 2005 and BizTalk 2006 installed.

Extract FailedOrchestrationRouting.zip to the root of the C:\

The following folders should be created:

C:\FailedOrchestrationRouting\bin
C:\FailedOrchestrationRouting\Files
C:\FailedOrchestrationRouting\obj

Run the samples
_______________

1) Navigate to folder:
C:\FailedOrchestrationRouting

Open Visual Studio Solution:
FailedOrchestrationRouting.sln

Check Deployment property page for correct Server and Configuration Database

2) Deploy

In Visual Studio right mouse button on the FailedOrchestrationRouting BizTalk project
and in the popup menu choose -> Deploy

Using the BizTalk 2006 Administration console, ensure that an Application called 
FailedOrchestrationRouting was created.


3) Import the Binding file and Start Application

Using the BizTalk 2006 Administration console, navigate to the 
FailedOrchestrationRouting application. Right mouse button on the 
FailedOrchestrationRouting application and in the popup menu choose:
Import -> Bindings

In the Import Bindings Dialog box, navigate to folder:
C:\FailedOrchestrationRouting

and then choose file:
Binding.xml

Right mouse button on the FailedOrchestrationRouting application and choose 
Start in the popup menu to start the application.

4) Test

Navigate to folder:
C:\FailedOrchestrationRouting\Files

Copy files:
TestMessageOK.xml -> Will Cause no Error
TestMessageThrowErrorOrchestration.xml -> Cause error in Orchestration
TestMessageThrowErrorPipeline.xml -> Cause error in pipeline

To folder:
C:\FailedOrchestrationRouting\Files\Receive

Navigate to Folder:
C:\FailedOrchestrationRouting\Files\Send

Two files should be visible:
a) Failed Message from Orchestration
b) Failed Message from Receive Port

To determine how things work, please examine the orchestrations in the BizTalk project and visit:
http://objectsharp.com/blogs/matt/archive/2006/11/01/10182.aspx