Debug BizTalk Custom Pipelines Components using Pipeline.exe utility – Pipeline file name is already specified Error

Posted: April 8, 2010 in BizTalk
Tags: , , , ,

While trying to debug custom pipeline component using “Pipeline.exe” utility, I keep getting the following error message:

Pipeline file name is already specified
Error 80131600

First of all, to use Pipeline utility to debug custom components you have to edit the properties of you pipeline component project:

  • Select you pipeline component project
  • Right click, and select the option “Properties”.
  • Select the tag Debug
    • In “Start Action”, select the option “Start external program” and select the Pipeline.exe utility
      • Common path: C:\Program Files\Microsoft BizTalk Server 2006\SDK\Utilities\PipelineToolsPipeline.exe
    • In “Start Options” you have to set the “Command line arguments” option:
      • “path to your pipeline.btp” –d “path to your message” –c

CAUSE

  • The path I was specifying to my.btp file wasn’t in quotes and spaces in the path were causing the problem
  • This apply also to the path of my message.

SOLUTION

  • Put the path with quotes, my sample:
    • “C:\Development\MyProject\MyPipelines\MyReceivePipeline.btp” -d “C:\Development\MyProjec\Samples\MY_Message.txt” -c

Tags: BizTalk | Pipeline | Components | Debug | Errors and Warnings, Causes and Solutions

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s