Biztalk Custom Pipeline Error

i have deployed my Custom pipeline and when i tried to use it it gives me the below error
There was a failure executing the receive pipeline: "BizTalk_Server_Project22.ReceivePipeline123, BizTalk Server Project22, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2f421c0b0e473f3a" Source: "Unknown " Receive Port: "ReceivePort8"
URI: "E:\rcv\gvgvg\*.xml" Reason: The pipeline component ClassLibrary123.filename,ClassLibrary123, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7cd997faca10c5d6 can not be found. If the component name is fully qualified, this error may occur
because the pipeline component can not be found in the assembly.
I have build the custom pipeline project placed the dll in the pipleine components and gac the same dll but i still get the below error
can you help me with this?

Do not put the Assembly in the %\Pipeline Components folder. Pipeline Components should be in the GAC only.
See here:
BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher
Make sure you're trying to put it in the correct GAC location. You cannot drop CLR 4.0 Assemblies in the Assemblies folder.
You muse use gacutil.exe to properly GAC any Assembly. There is an example in the above Wiki Article along with all other steps to use a custom Pipeline Component.

Similar Messages

BizTalk Send Pipeline Error 0xc0c01658

Hello,
I created a Send Pipeline that has a Flat File Assembler. When I tried to send the Message I am getting error like, Error Code 0xc0c01658 (Send Pipeline Error)
The detail of the error,
There was a failure executing the send pipeline. Please verify that the pipeline strong name is correct and that the pipeline assembly
can anyone help me, I am new to BizTalk and I am learning
Thanks

I tried doing it Johns but still shows the same error.
Does file go though if you put pass thru pipeline? If so it means everything else in project is working ok.
After that, check if your project containing pipeline builds ok and is in GAC.
Add your pipeline in send port again.Restart host instances, and stop/start your application if that helps?

Biztalk Recive pipeline Error

Hi,
I am using the Flat File disassembeler in my recive pipeline when i send my csv file through it
There was a failure executing the receive pipeline: PublicKeyToken=e288d30601a470cf" Source: "Pipeline " Receive Port: "RcvDaxdfsdExtractPort" URI: "C:\0_AS_SharedFolders\Receive\ClearingSettlementExsdsftract\*.csv" Reason:
An error occurred when parsing the incoming document: "Unexpected end of stream while looking for:
'\r\n'
The current definition being parsed is . The stream offset where the error occured is 20431. The line number where the error occured is 417. The column where the error occured is 47.".
my csv file content is
20140302190,CBO0011680690,2014-03-06 11:40:41,,
20140302190,CBO0011680690,2014-03-06 11:52:13,,
20140306008,CBO0011680646,2014-03-06 11:33:14,,
20140306008,CBO0011680646,2014-03-06 11:52:54,,
20140306011,CBO0011680643,2014-03-06 11:41:01,,
20140306011,CBO0011680643,2014-03-06 11:46:43,,
20140306012,CBO0011680642,2014-03-06 11:37:08,,
20140306012,CBO0011680642,2014-03-06 11:46:39,,
20140306013,CBO0011680644,2014-03-06 11:38:17,,
20140306013,CBO0011680644,2014-03-06 11:46:46,,
20140306013,CBO0011680645,2014-03-06 11:36:02,,
20140306013,CBO0011680645,2014-03-06 11:36:49,,
20140306015,CBO0011680666,2014-03-06 11:33:24,,
20140306015,CBO0011680666,2014-03-06 11:52:58,,
20140306018,CBO0011680661,2014-03-06 11:42:01,,
20140306018,CBO0011680661,2014-03-06 11:46:57,,
20140306019,CBO0011680658,2014-03-06 11:38:23,,
20140306019,CBO0011680658,2014-03-06 11:46:52,,
20140306020,CBO0011680656,2014-03-06 11:38:20,,
20140306020,CBO0011680656,2014-03-06 11:46:49,,
20140306020,CBO0011680657,2014-03-06 11:35:04,,
20140306020,CBO0011680657,2014-03-06 11:36:46,,
20140306021,CBO0011680659,2014-03-06 11:37:50,,
20140306021,CBO0011680659,2014-03-06 11:46:55,,
20140306022,CBO0011680663,2014-03-06 11:36:05,,
20140306022,CBO0011680663,2014-03-06 11:36:43,,
20140306023,CBO0011680655,2014-03-06 11:38:54,,
20140306023,CBO0011680655,2014-03-06 11:49:44,,
20140306024,CBO0011680653,2014-03-06 11:36:58,,
20140306024,CBO0011680653,2014-03-06 11:49:41,,
20140306024,CBO0011680654,2014-03-06 11:33:21,,
20140306024,CBO0011680654,2014-03-06 11:37:18,,
20140306028,CBO0011680652,2014-03-06 11:40:27,,
20140306028,CBO0011680652,2014-03-06 11:48:47,,
20140306029,CBO0011680650,2014-03-06 11:37:29,,
20140306029,CBO0011680650,2014-03-06 11:48:45,,
20140306029,CBO0011680651,2014-03-06 11:33:18,,
20140306029,CBO0011680651,2014-03-06 11:38:08,,
20140306030,CBO0011680668,2014-03-06 11:37:21,,
20140306031,CBO0011680664,2014-03-06 11:38:15,,
20140306031,CBO0011680664,2014-03-06 11:50:34,,
20140306032,CBO0011680665,2014-03-06 11:40:03,,
20140306032,CBO0011680665,2014-03-06 11:51:25,,
20140306034,CBO0011680685,2014-03-06 11:33:29,,
20140306034,CBO0011680685,2014-03-06 11:53:03,,
20140306037,CBO0011680680,2014-03-06 11:42:04,,
20140306037,CBO0011680680,2014-03-06 11:48:35,,
20140306038,CBO0011680675,2014-03-06 11:37:47,,
20140306038,CBO0011680675,2014-03-06 11:48:28,,
20140306039,CBO0011680673,2014-03-06 11:38:45,,
20140306039,CBO0011680673,2014-03-06 11:48:25,,
20140306040,CBO0011680676,2014-03-06 11:38:11,,
20140306040,CBO0011680676,2014-03-06 11:48:30,,
20140306041,CBO0011680678,2014-03-06 11:39:18,,
20140306041,CBO0011680678,2014-03-06 11:48:33,,
20140306041,CBO0011680679,2014-03-06 11:35:42,,
20140306041,CBO0011680679,2014-03-06 11:36:52,,
20140306042,CBO0011680672,2014-03-06 11:37:57,,
20140306042,CBO0011680672,2014-03-06 11:49:46,,
20140306045,CBO0011680683,2014-03-06 11:40:08,,
20140306045,CBO0011680683,2014-03-06 11:50:08,,
20140306046,CBO0011680681,2014-03-06 11:36:55,,
20140306046,CBO0011680681,2014-03-06 11:50:05,,
20140306046,CBO0011680682,2014-03-06 11:33:26,,
20140306046,CBO0011680682,2014-03-06 11:37:11,,
20140306047,CBO0011680687,2014-03-06 11:37:15,,
20140306048,CBO0011680684,2014-03-06 11:38:30,,
20140306048,CBO0011680684,2014-03-06 11:50:36,,
20140306051,CBO0011680693,2014-03-06 11:37:23,,
20140306052,CBO0011680692,2014-03-06 11:39:32,,
20140306052,CBO0011680692,2014-03-06 11:51:28,,
20140306053,CBO0011680740,2014-03-06 11:33:54,,
20140306053,CBO0011680740,2014-03-06 11:54:00,,
20140306053,CBO0011680748,2014-03-06 11:47:27,,
20140306059,CBO0011680715,2014-03-06 11:45:09,,
20140306059,CBO0011680715,2014-03-06 11:47:18,,
20140306060,CBO0011680710,2014-03-06 11:43:11,,
20140306060,CBO0011680710,2014-03-06 11:47:09,,
20140306061,CBO0011680708,2014-03-06 11:39:50,,
20140306061,CBO0011680708,2014-03-06 11:47:06,,
20140306061,CBO0011680709,2014-03-06 11:35:08,,
20140306061,CBO0011680709,2014-03-06 11:37:04,,
20140306062,CBO0011680704,2014-03-06 11:41:50,,
20140306062,CBO0011680704,2014-03-06 11:47:00,,
20140306063,CBO0011680706,2014-03-06 11:39:01,,
20140306063,CBO0011680706,2014-03-06 11:47:03,,
20140306064,CBO0011680711,2014-03-06 11:41:53,,
20140306064,CBO0011680711,2014-03-06 11:47:13,,
20140306065,CBO0011680713,2014-03-06 11:43:17,,
20140306065,CBO0011680713,2014-03-06 11:47:16,,
20140306065,CBO0011680714,2014-03-06 11:35:23,,
20140306065,CBO0011680714,2014-03-06 11:38:33,,
20140306066,CBO0011680716,2014-03-06 11:39:57,,
20140306066,CBO0011680716,2014-03-06 11:47:21,,
20140306067,CBO0011680718,2014-03-06 11:41:07,,
20140306067,CBO0011680718,2014-03-06 11:47:24,,
20140306067,CBO0011680719,2014-03-06 11:36:08,,
20140306067,CBO0011680719,2014-03-06 11:38:01,,
20140306068,CBO0011680737,2014-03-06 11:33:52,,
20140306068,CBO0011680737,2014-03-06 11:53:08,,
20140306069,CBO0011680736,2014-03-06 11:33:49,,
20140306069,CBO0011680736,2014-03-06 11:53:05,,
20140306070,CBO0011680760,2014-03-06 11:39:26,,
20140306072,CBO0011680703,2014-03-06 11:43:37,,
20140306072,CBO0011680703,2014-03-06 11:49:51,,
20140306073,CBO0011680701,2014-03-06 11:41:31,,
20140306073,CBO0011680701,2014-03-06 11:49:48,,
20140306073,CBO0011680702,2014-03-06 11:33:37,,
20140306073,CBO0011680702,2014-03-06 11:42:54,,
20140306074,CBO0011680739,2014-03-06 11:34:49,,
20140306074,CBO0011680739,2014-03-06 11:53:50,,
20140306074,CBO0011680747,2014-03-06 11:48:57,,
20140306075,CBO0011680743,2014-03-06 11:39:55,,
20140306075,CBO0011680743,2014-03-06 11:48:55,,
20140306080,CBO0011680697,2014-03-06 11:44:09,,
20140306080,CBO0011680697,2014-03-06 11:48:52,,
20140306081,CBO0011680695,2014-03-06 11:39:44,,
20140306081,CBO0011680695,2014-03-06 11:48:50,,
20140306081,CBO0011680696,2014-03-06 11:33:32,,
20140306081,CBO0011680696,2014-03-06 11:40:48,,
20140306082,CBO0011680759,2014-03-06 11:40:37,,
20140306085,CBO0011680700,2014-03-06 11:41:04,,
20140306085,CBO0011680700,2014-03-06 11:49:25,,
20140306086,CBO0011680698,2014-03-06 11:38:05,,
20140306086,CBO0011680698,2014-03-06 11:49:23,,
20140306086,CBO0011680699,2014-03-06 11:33:34,,
20140306086,CBO0011680699,2014-03-06 11:39:04,,
20140306089,CBO0011680722,2014-03-06 11:43:22,,
20140306089,CBO0011680722,2014-03-06 11:50:14,,
20140306090,CBO0011680720,2014-03-06 11:39:35,,
20140306090,CBO0011680720,2014-03-06 11:50:11,,
20140306090,CBO0011680721,2014-03-06 11:33:39,,
20140306090,CBO0011680721,2014-03-06 11:40:32,,
20140306091,CBO0011680761,2014-03-06 11:37:44,,
20140306092,CBO0011680741,2014-03-06 11:35:29,,
20140306092,CBO0011680741,2014-03-06 11:53:48,,
20140306092,CBO0011680749,2014-03-06 11:50:44,,
20140306095,CBO0011680725,2014-03-06 11:44:51,,
20140306095,CBO0011680725,2014-03-06 11:50:41,,
20140306096,CBO0011680723,2014-03-06 11:42:35,,
20140306096,CBO0011680723,2014-03-06 11:50:38,,
20140306096,CBO0011680724,2014-03-06 11:33:42,,
20140306096,CBO0011680724,2014-03-06 11:43:42,,
20140306099,CBO0011680728,2014-03-06 11:43:47,,
20140306099,CBO0011680728,2014-03-06 11:51:03,,
20140306100,CBO0011680726,2014-03-06 11:40:59,,
20140306100,CBO0011680726,2014-03-06 11:51:00,,
20140306100,CBO0011680727,2014-03-06 11:33:44,,
20140306100,CBO0011680727,2014-03-06 11:42:15,,
20140306101,CBO0011680762,2014-03-06 11:39:09,,
20140306102,CBO0011680742,2014-03-06 11:36:14,,
20140306102,CBO0011680742,2014-03-06 11:53:11,,
20140306106,CBO0011680734,2014-03-06 11:43:14,,
20140306106,CBO0011680734,2014-03-06 11:51:32,,
20140306107,CBO0011680732,2014-03-06 11:40:11,,
20140306107,CBO0011680732,2014-03-06 11:51:30,,
20140306107,CBO0011680733,2014-03-06 11:33:47,,
20140306107,CBO0011680733,2014-03-06 11:41:19,,
20140306108,CBO0011680735,2014-03-06 11:37:26,,
20140306108,CBO0011680735,2014-03-06 11:51:35,,
20140306109,CBO0011680738,2014-03-06 11:36:11,,
20140306109,CBO0011680738,2014-03-06 11:52:40,,
20140306111,CBO0011680731,2014-03-06 11:44:06,,
20140306111,CBO0011680731,2014-03-06 11:52:03,,
20140306113,CBO0011680729,2014-03-06 11:43:02,,
20140306113,CBO0011680729,2014-03-06 11:52:16,,
20140306114,CBO0011680730,2014-03-06 11:38:57,,
20140306114,CBO0011680730,2014-03-06 11:52:19,,
20140306115,CBO0011680763,2014-03-06 11:37:35,,
20140306116,CBO0011680821,2014-03-06 11:34:20,,
20140306116,CBO0011680821,2014-03-06 11:54:11,,
20140306116,CBO0011680838,2014-03-06 11:48:00,,
20140306117,CBO0011680827,2014-03-06 11:42:37,,
20140306117,CBO0011680827,2014-03-06 11:47:57,,
20140306123,CBO0011680793,2014-03-06 11:45:17,,
20140306123,CBO0011680793,2014-03-06 11:47:46,,
20140306124,CBO0011680788,2014-03-06 11:44:24,,
20140306124,CBO0011680788,2014-03-06 11:47:39,,
20140306125,CBO0011680786,2014-03-06 11:43:05,,
20140306125,CBO0011680786,2014-03-06 11:47:36,,
20140306125,CBO0011680787,2014-03-06 11:35:10,,
20140306125,CBO0011680787,2014-03-06 11:38:27,,
20140306126,CBO0011680782,2014-03-06 11:43:25,,
20140306126,CBO0011680782,2014-03-06 11:47:30,,
20140306127,CBO0011680784,2014-03-06 11:41:47,,
20140306127,CBO0011680784,2014-03-06 11:47:34,,
20140306128,CBO0011680789,2014-03-06 11:43:20,,
20140306128,CBO0011680789,2014-03-06 11:47:41,,
20140306129,CBO0011680791,2014-03-06 11:44:14,,
20140306129,CBO0011680791,2014-03-06 11:47:44,,
20140306129,CBO0011680792,2014-03-06 11:35:32,,
20140306129,CBO0011680792,2014-03-06 11:39:28,,
20140306130,CBO0011680794,2014-03-06 11:43:08,,
20140306130,CBO0011680794,2014-03-06 11:47:49,,
20140306131,CBO0011680796,2014-03-06 11:42:40,,
20140306131,CBO0011680796,2014-03-06 11:47:53,,
20140306131,CBO0011680797,2014-03-06 11:36:18,,
20140306131,CBO0011680797,2014-03-06 11:39:06,,
20140306132,CBO0011680815,2014-03-06 11:34:17,,
20140306132,CBO0011680815,2014-03-06 11:53:36,,
20140306133,CBO0011680814,2014-03-06 11:34:15,,
20140306133,CBO0011680814,2014-03-06 11:53:38,,
20140306134,CBO0011680865,2014-03-06 11:41:16,,
20140306137,CBO0011680820,2014-03-06 11:35:13,,
20140306137,CBO0011680820,2014-03-06 11:53:00,,
20140306139,CBO0011680781,2014-03-06 11:44:33,,
20140306139,CBO0011680781,2014-03-06 11:49:55,,
20140306140,CBO0011680779,2014-03-06 11:42:51,,
20140306140,CBO0011680779,2014-03-06 11:49:53,,
20140306140,CBO0011680780,2014-03-06 11:34:02,,
20140306140,CBO0011680780,2014-03-06 11:44:01,,
20140306142,CBO0011680818,2014-03-06 11:34:52,,
20140306142,CBO0011680818,2014-03-06 11:54:05,,
20140306142,CBO0011680836,2014-03-06 11:49:07,,
20140306143,CBO0011680826,2014-03-06 11:41:34,,
20140306143,CBO0011680826,2014-03-06 11:49:04,,
20140306150,CBO0011680775,2014-03-06 11:45:06,,
20140306150,CBO0011680775,2014-03-06 11:49:02,,
20140306151,CBO0011680773,2014-03-06 11:42:17,,
20140306151,CBO0011680773,2014-03-06 11:48:59,,
20140306151,CBO0011680774,2014-03-06 11:33:57,,
20140306151,CBO0011680774,2014-03-06 11:43:28,,
20140306152,CBO0011680863,2014-03-06 11:42:32,,
20140306155,CBO0011680819,2014-03-06 11:34:58,,
20140306155,CBO0011680819,2014-03-06 11:53:22,,
20140306155,CBO0011680837,2014-03-06 11:49:33,,
20140306158,CBO0011680778,2014-03-06 11:44:16,,
20140306158,CBO0011680778,2014-03-06 11:49:30,,
20140306159,CBO0011680776,2014-03-06 11:41:10,,
20140306159,CBO0011680776,2014-03-06 11:49:28,,
20140306159,CBO0011680777,2014-03-06 11:34:00,,
20140306159,CBO0011680777,2014-03-06 11:42:29,,
20140306160,CBO0011680864,2014-03-06 11:39:38,,
20140306162,CBO0011680822,2014-03-06 11:35:18,,
20140306162,CBO0011680822,2014-03-06 11:53:42,,
20140306162,CBO0011680839,2014-03-06 11:50:24,,
20140306163,CBO0011680828,2014-03-06 11:36:38,,
20140306169,CBO0011680800,2014-03-06 11:44:27,,
20140306169,CBO0011680800,2014-03-06 11:50:21,,
20140306170,CBO0011680798,2014-03-06 11:40:30,,
20140306170,CBO0011680798,2014-03-06 11:50:16,,
20140306170,CBO0011680799,2014-03-06 11:34:05,,
20140306170,CBO0011680799,2014-03-06 11:41:55,,
20140306171,CBO0011680866,2014-03-06 11:40:35,,
20140306173,CBO0011680823,2014-03-06 11:35:34,,
20140306173,CBO0011680823,2014-03-06 11:53:58,,
20140306173,CBO0011680840,2014-03-06 11:50:50,,
20140306176,CBO0011680803,2014-03-06 11:45:04,,
20140306176,CBO0011680803,2014-03-06 11:50:48,,
20140306177,CBO0011680801,2014-03-06 11:43:32,,
20140306177,CBO0011680801,2014-03-06 11:50:46,,
20140306177,CBO0011680802,2014-03-06 11:34:07,,
20140306177,CBO0011680802,2014-03-06 11:44:19,,
20140306179,CBO0011680824,2014-03-06 11:35:54,,
20140306179,CBO0011680824,2014-03-06 11:53:29,,
20140306179,CBO0011680841,2014-03-06 11:51:16,,
20140306180,CBO0011680829,2014-03-06 11:37:32,,
20140306180,CBO0011680829,2014-03-06 11:51:13,,
20140306183,CBO0011680806,2014-03-06 11:44:38,,
20140306183,CBO0011680806,2014-03-06 11:51:10,,
20140306184,CBO0011680804,2014-03-06 11:42:23,,
20140306184,CBO0011680804,2014-03-06 11:51:07,,
20140306184,CBO0011680805,2014-03-06 11:34:10,,
20140306184,CBO0011680805,2014-03-06 11:43:34,,
20140306185,CBO0011680816,2014-03-06 11:35:50,,
20140306185,CBO0011680816,2014-03-06 11:52:38,,
20140306186,CBO0011680867,2014-03-06 11:40:06,,
20140306188,CBO0011680825,2014-03-06 11:36:23,,
20140306188,CBO0011680825,2014-03-06 11:53:44,,
20140306188,CBO0011680842,2014-03-06 11:51:49,,
20140306189,CBO0011680830,2014-03-06 11:37:01,,
20140306189,CBO0011680830,2014-03-06 11:51:45,,
20140306195,CBO0011680812,2014-03-06 11:44:48,,
20140306195,CBO0011680812,2014-03-06 11:51:39,,
20140306196,CBO0011680810,2014-03-06 11:42:20,,
20140306196,CBO0011680810,2014-03-06 11:51:37,,
20140306196,CBO0011680811,2014-03-06 11:34:12,,
20140306196,CBO0011680811,2014-03-06 11:43:50,,
20140306197,CBO0011680813,2014-03-06 11:38:51,,
20140306197,CBO0011680813,2014-03-06 11:51:42,,
20140306198,CBO0011680817,2014-03-06 11:36:21,,
20140306198,CBO0011680817,2014-03-06 11:52:45,,
20140306200,CBO0011680809,2014-03-06 11:44:59,,
20140306200,CBO0011680809,2014-03-06 11:52:05,,
20140306202,CBO0011680807,2014-03-06 11:45:12,,
20140306202,CBO0011680807,2014-03-06 11:52:22,,
20140306203,CBO0011680808,2014-03-06 11:42:12,,
20140306203,CBO0011680808,2014-03-06 11:52:25,,
20140306204,CBO0011680868,2014-03-06 11:42:09,,
20140306205,CBO0011680928,2014-03-06 11:34:44,,
20140306205,CBO0011680928,2014-03-06 11:54:07,,
20140306205,CBO0011680948,2014-03-06 11:48:40,,
20140306206,CBO0011680935,2014-03-06 11:42:25,,
20140306206,CBO0011680935,2014-03-06 11:48:37,,
20140306210,CBO0011680939,2014-03-06 11:38:47,,
20140306210,CBO0011680994,2014-03-06 11:48:42,,
20140306210,CBO0011680994,2014-03-06 11:52:51,,
20140306213,CBO0011680902,2014-03-06 11:45:14,,
20140306213,CBO0011680902,2014-03-06 11:48:18,,
20140306214,CBO0011680897,2014-03-06 11:44:03,,
20140306214,CBO0011680897,2014-03-06 11:48:10,,
20140306215,CBO0011680895,2014-03-06 11:44:12,,
20140306215,CBO0011680895,2014-03-06 11:48:08,,
20140306215,CBO0011680896,2014-03-06 11:35:15,,
20140306215,CBO0011680896,2014-03-06 11:39:20,,
20140306216,CBO0011680891,2014-03-06 11:43:53,,
20140306216,CBO0011680891,2014-03-06 11:48:03,,
20140306217,CBO0011680893,2014-03-06 11:42:57,,
20140306217,CBO0011680893,2014-03-06 11:48:05,,
20140306218,CBO0011680898,2014-03-06 11:42:48,,
20140306218,CBO0011680898,2014-03-06 11:48:13,,
20140306219,CBO0011680900,2014-03-06 11:44:21,,
20140306219,CBO0011680900,2014-03-06 11:48:15,,
20140306219,CBO0011680901,2014-03-06 11:35:38,,
20140306219,CBO0011680901,2014-03-06 11:39:41,,
20140306220,CBO0011680903,2014-03-06 11:43:44,,
20140306220,CBO0011680903,2014-03-06 11:48:20,,
20140306221,CBO0011680905,2014-03-06 11:43:00,,
20140306221,CBO0011680905,2014-03-06 11:48:23,,
20140306221,CBO0011680906,2014-03-06 11:36:26,,
20140306221,CBO0011680906,2014-03-06 11:39:12,,
20140306222,CBO0011680924,2014-03-06 11:34:41,,
20140306222,CBO0011680924,2014-03-06 11:53:25,,
20140306223,CBO0011680923,2014-03-06 11:34:38,,
20140306223,CBO0011680923,2014-03-06 11:53:15,,
20140306224,CBO0011680975,2014-03-06 11:41:26,,
20140306227,CBO0011680996,2014-03-06 11:40:00,,
20140306227,CBO0011680996,2014-03-06 11:50:02,,
20140306228,CBO0011680890,2014-03-06 11:43:58,,
20140306228,CBO0011680890,2014-03-06 11:50:00,,
20140306229,CBO0011680888,2014-03-06 11:40:22,,
20140306229,CBO0011680888,2014-03-06 11:49:58,,
20140306229,CBO0011680889,2014-03-06 11:34:28,,
20140306229,CBO0011680889,2014-03-06 11:41:44,,
20140306230,CBO0011680926,2014-03-06 11:34:55,,
20140306230,CBO0011680926,2014-03-06 11:53:55,,
20140306230,CBO0011680946,2014-03-06 11:49:16,,
20140306231,CBO0011680934,2014-03-06 11:40:43,,
20140306231,CBO0011680934,2014-03-06 11:49:14,,
20140306232,CBO0011680995,2014-03-06 11:41:22,,
20140306232,CBO0011680995,2014-03-06 11:49:21,,
20140306237,CBO0011680938,2014-03-06 11:38:36,,
20140306237,CBO0011680993,2014-03-06 11:49:18,,
20140306237,CBO0011680993,2014-03-06 11:52:48,,
20140306239,CBO0011680884,2014-03-06 11:44:43,,
20140306239,CBO0011680884,2014-03-06 11:49:12,,
20140306240,CBO0011680882,2014-03-06 11:39:47,,
20140306240,CBO0011680882,2014-03-06 11:49:09,,
20140306240,CBO0011680883,2014-03-06 11:34:22,,
20140306240,CBO0011680883,2014-03-06 11:40:53,,
20140306241,CBO0011680974,2014-03-06 11:40:25,,
20140306244,CBO0011680927,2014-03-06 11:35:02,,
20140306244,CBO0011680927,2014-03-06 11:53:17,,
20140306244,CBO0011680947,2014-03-06 11:49:39,,
20140306247,CBO0011680887,2014-03-06 11:42:43,,
20140306247,CBO0011680887,2014-03-06 11:49:37,,
20140306248,CBO0011680885,2014-03-06 11:39:52,,
20140306248,CBO0011680885,2014-03-06 11:49:35,,
20140306248,CBO0011680886,2014-03-06 11:34:25,,
20140306248,CBO0011680886,2014-03-06 11:40:56,,
20140306250,CBO0011680929,2014-03-06 11:35:20,,
20140306250,CBO0011680929,2014-03-06 11:53:33,,
20140306250,CBO0011680949,2014-03-06 11:50:31,,
20140306251,CBO0011680936,2014-03-06 11:36:41,,
20140306258,CBO0011680909,2014-03-06 11:42:46,,
20140306258,CBO0011680909,2014-03-06 11:50:29,,
20140306259,CBO0011680907,2014-03-06 11:38:42,,
20140306259,CBO0011680907,2014-03-06 11:50:26,,
20140306259,CBO0011680908,2014-03-06 11:34:30,,
20140306259,CBO0011680908,2014-03-06 11:39:23,,
20140306260,CBO0011680976,2014-03-06 11:41:12,,
20140306262,CBO0011680930,2014-03-06 11:35:45,,
20140306262,CBO0011680930,2014-03-06 11:53:53,,
20140306262,CBO0011680950,2014-03-06 11:50:58,,
20140306265,CBO0011680912,2014-03-06 11:44:41,,
20140306265,CBO0011680912,2014-03-06 11:50:55,,
20140306266,CBO0011680910,2014-03-06 11:40:51,,
20140306266,CBO0011680910,2014-03-06 11:50:53,,
20140306266,CBO0011680911,2014-03-06 11:34:32,,
20140306266,CBO0011680911,2014-03-06 11:42:06,,
20140306268,CBO0011680931,2014-03-06 11:35:59,,
20140306268,CBO0011680931,2014-03-06 11:53:20,,
20140306269,CBO0011680937,2014-03-06 11:37:53,,
20140306269,CBO0011680937,2014-03-06 11:51:23,,
20140306273,CBO0011680915,2014-03-06 11:43:55,,
20140306273,CBO0011680915,2014-03-06 11:51:20,,
20140306274,CBO0011680913,2014-03-06 11:40:46,,
20140306274,CBO0011680913,2014-03-06 11:51:18,,
20140306274,CBO0011680914,2014-03-06 11:34:35,,
20140306274,CBO0011680914,2014-03-06 11:41:58,,
20140306275,CBO0011680977,2014-03-06 11:39:15,,
20140306277,CBO0011680933,2014-03-06 11:36:33,,
20140306277,CBO0011680933,2014-03-06 11:53:27,,
20140306278,CBO0011680998,2014-03-06 11:41:37,,
20140306278,CBO0011680998,2014-03-06 11:52:00,,
20140306281,CBO0011680921,2014-03-06 11:44:36,,
20140306281,CBO0011680921,2014-03-06 11:51:55,,
20140306282,CBO0011680919,2014-03-06 11:40:17,,
20140306282,CBO0011680919,2014-03-06 11:51:52,,
20140306282,CBO0011680920,2014-03-06 11:34:46,,
20140306282,CBO0011680920,2014-03-06 11:41:41,,
20140306283,CBO0011680922,2014-03-06 11:37:38,,
20140306283,CBO0011680922,2014-03-06 11:51:58,,
20140306284,CBO0011680925,2014-03-06 11:36:30,,
20140306284,CBO0011680925,2014-03-06 11:52:43,,
20140306286,CBO0011680918,2014-03-06 11:44:55,,
20140306286,CBO0011680918,2014-03-06 11:52:07,,
20140306287,CBO0011680932,2014-03-06 11:36:36,,
20140306287,CBO0011680932,2014-03-06 11:54:03,,
20140306287,CBO0011680951,2014-03-06 11:52:33,,
20140306288,CBO0011680997,2014-03-06 11:44:46,,
20140306288,CBO0011680997,2014-03-06 11:52:35,,
20140306295,CBO0011680916,2014-03-06 11:43:40,,
20140306295,CBO0011680916,2014-03-06 11:52:28,,
20140306296,CBO0011680917,2014-03-06 11:37:42,,
20140306296,CBO0011680917,2014-03-06 11:52:30,,
20140306297,CBO0011680978,2014-03-06 11:44:30,,
can you tell me how to debug this?

Hi Sujith,
The flat-file schema you have created doesn't match the instance you're testing with. One possible reasons for this error is that schema you have created could be expected carriage-return at
the end of the last record, but the instance you're testing with may not have it..
So I have created a schema for your instance flat file and this schema expects the last line to have carriage-return to denote as end of the record, may be similar to yours.
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" xmlns="http://TryBizTalk.FF_Schema.FlatFileSchema1" targetNamespace="http://TryBizTalk.FF_Schema.FlatFileSchema1" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<schemaEditorExtension:schemaInfo namespaceAlias="b" extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension" standardName="Flat File" xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
<b:schemaInfo standard="Flat File" codepage="65001" default_pad_char=" " pad_char_type="char" count_positions_by_byte="false" parser_optimization="speed" lookahead_depth="3" suppress_empty_nodes="false" generate_empty_nodes="true" allow_early_termination="false" early_terminate_optional_fields="false" allow_message_breakup_of_infix_root="false" compile_parse_tables="false" root_reference="DataExtractDetails" />
</xs:appinfo>
</xs:annotation>
<xs:element name="DataExtractDetails">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" child_delimiter_type="hex" child_delimiter="0xD 0xA" child_order="postfix" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element maxOccurs="unbounded" name="DataExtractDetail">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited" child_delimiter_type="char" child_delimiter="," child_order="infix" sequence_number="1" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003" />
</xs:appinfo>
</xs:annotation>
<xs:element name="DE_ID" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="DE_ref" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="2" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="DE_DateTime" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="3" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="DataExtractDetail_Child4" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="4" />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="DataExtractDetail_Child5" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="5" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
So, If you test this schema with your flat-file instance, where the last line have carriage-return as below, this will work.Here carriage-return denotes the end of the record:
If you test the schema with flat-file instance like the below, where there is no carriage-return at the end of the last line
Then you will have error as you have now.
Try to test the flat-file which matches to the schema (or create a flat-file schema which matches to the flat-file instance) . If you don't expect carriage-return at the last line of the flat-file, then select the root element and set its childorder
property to "infix" otherwise "postfix".
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Biztalk Receive pipeline error

There was a failure executing the receive pipeline: "ABC Pipeline, ÄBCPipeline Version=1.0.0.0, Culture=neutral, PublicKeyToken=27fe5b80934cb26ba" Source: "Pipeline " Receive Port: "ABC.Port.ABCData_ReceivePort" Reason: The
document failed to validate because of the following error:"The element 'ProcessRecord' has invalid child element 'XYZ'. List of possible elements expected: 'OrderCompletionDate'." .
TVS Apache

RFC_ERROR_SYSTEM_FAILURE occurs if something is wrong with the Sap system that you are connecting to.
The most common cause is the RFC, you are calling itself has thrown an exception during the runtime.
This will help you in figuring out the cause of the issue:
1. Call the same RFC with same parameters in SapGui and see if it is successful.
2. Turn on Rfc tracing and look into the trace files.
If you are not able to find the cause, you can contact SAP/ABAP consultant with the traces. They will
be able to help you with this further.
If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Custom Pipeline code creation wizard in BizTalk

Hi - how is that I can follow the wizard in BizTalk to create or build a Custom Pipeline component, all the structure will be created by itself, I just need to go and in execute method write my code.
Please can anyone mention the steps ?
MBH

Hi Jag,
From the download page,
http://btsplcw.codeplex.com/releases/view/46419, download the correct version for your use, i.e., for VS 2008 or VS 2010]
Open the PipeLineComponentWizard.sln
Build PipelineComponentWizard.sln
Navigate to PipelineComponentWizard Setup Folder. You can find the setup.exe and PipelineComponentWizard Setup.msi in the Debug/Release folder.
Run the Setup.exe.
And for further steps, follow the guidlines as suggested in the following document (one of the users has shaped a step-by-step document to use this wizard and create a pipeline)
http://gallery.technet.microsoft.com/Custom-Pipelines-using-the-0f7be626
Also I would urge you to learn about the custom pipeline component development. Following refernces shall help you:
http://msdn.microsoft.com/en-gb/library/aa548050.aspx
http://blogs.msdn.com/b/brajens/archive/2006/11/25/how-to-develop-biztalk-custom-pipeline-components-part1.aspx
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

BizTalk:How to share customized pipeline with more than one BizTalk Application

I have a new BizTalk application which will use a customize generic pipeline . This pipeline has been used in an existing BizTalk application.
When I use BizTalk Server Administration to add this pipeline assembly as a resource for a new BizTalk application, it shows error message: "this biztalk assembley has already in store and is either associated with another application or another type".
My questions is how to share the generic pipeline component with many BizTalk application?
Many Thanks.

Hi,
If you plan on using the deployed pipeline across multiple applications in BizTalk you have two options:
1) The Current Application (in BizTalk Server Administration Console) should have the other application [where the pipeline
is deployed] as reference.
right click the "Current Application" and select "Properties"
on the "Properties" page, left hand side, select "References"
On the right-hand side, use "Add" to add the "Other Application" as a reference.
Refer: How
to Add a BizTalk Assembly to an Application
Doing so will ensure that ALL resources (maps, schemas, orchestrations, send ports, receive locations, rules, etc.) deployed
for "Other Application" are available/reprehensible in "Current Application".
2) Create a common BizTalk application on BizTalk Admin Console and add your custom pipeline assembly in that new application
as a resource. With this, you don't need any other application to be started apart from this common application. Any other application who wants to use this pipeline will refer this common application.
Rachit
Please mark as answer or vote as helpful if my reply does

Custom Pipeline Component error

I have created a custom pipeline component which references a template file on the local drive e.g. c:\test\template.xlsx. however when I run the application the Send pipeline fails Reason: 'c:\test\template.xlsx' could not be found.
It does exist, everything is spelt correctly and the host account has access to the folder. Why can't the component see it?
----------------<0>----------------
http://redeyedmonster.co.uk
----------------<0>----------------

I tried a code as highlighted by Rachit, but I don’t see issue as the referred blog suggest.
Coming to questioners code, I created a quick pipeline component which uses a dll for
Microsoft.Office.Interop.Excel
accessing the excel files and does something with Excel file.
Few things I want to highlight here.
If the questioner (RedEyeMonster) is using the same dll (Microsoft.Office.Interop.Excel)
in the pipeline component as I used, then I am afraid Workbooks.Open’s component doesn’t just take one parameter as shown.
Open method doesn’t have any overloaded methods. It takes few parameter and its worth checking each one on them.Some of the parameter are very important and could cause issues (like
ReadOnly , IgnoreReadOnlyRecommended, Editable etc). As said, the
Workbooks .Open method doesn’t just have template file location parameter. It’s worth reviewing the code again.
Microsoft.Office.Interop.Excel.Application excelApplication = new Microsoft.Office.Interop.Excel.Application();
//When I tried without the following couple of lines, my program waited for long time and crashed
excelApplication.DisplayAlerts = false;
excelApplication.Visible = true;
Microsoft.Office.Interop.Excel.Workbook excelWorkboook = excelApplication.Workbooks.Open(@"C:\MRAshwinPrabhu\TestExcel.xsl", 2, false,
5, "", "", true, Microsoft.Office.Interop.Excel.XlPlatform.xlWindows, "",
false, false, 0, false, true, 0);
While trying the code, I create a excel file as extension *.xls (older version of Excel 97-2003 workbook) and in the code I tried to open the file as “C:\foldername\FileName.xlsx”.
*.xls and *.xlsx are different, though in the folder the excel icon may look similar they are different file extensions. I for the same error as the questioner.
Also issue I faced while trying this is “DisplayAlerts”
property. When I tried without setting this property to false, my program just waited for long time and crached evently. So when you use in a program like pipeline where you don’t have UI, ensure this property is set to false.
Hope the above suggest would help the questioner.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

How to use custom pipeline dlls in Biztalk Projects so that they appear in the send/receive pipeline configuration after deployment?

I have a existing Biztalk application that uses custom pipelines for receiving excel files. I have the dll of that custom pipeline. Now i created another BT application that needs to use that same custom pipeline. But after i deploy the application in
Biztalk, i can't see the pipeline available in Receive pipeline configuration combo box during configuration. I have referenced the custom pipeline dll in my project before deploying, but that doesn't help. I also copied the dll in the C:\Program Files
(x86)\Microsoft BizTalk Server 2010\Pipeline Components folder and C:\Program Files (x86)\Microsoft BizTalk Server 2010 folder, but that doesn't make the pipelines appear during configuration too.
Can anyone give any idea on how can i use these custom pipeline dlls in project so that they appear in configuration after deployment?

If you plan on using the deployed pipeline across multiple applications in BizTalk, the BizTalk Application (using the BizTalk Server Administration Console) should have the other application [where the pipeline is deployed] as reference.
For e.g.: Custom Pipeline (myCustomPipeline) part of a BizTalk Project (dll - myCustomProject.dll) deployed under Application [Some Application] also to be used in another BizTalk Application [Some Other Applicaiton] then using BizTalk Server Administartor
right click the "Some Other Application" and select "Properties"
on the "Properties" page, left hand side, select "References"
on the right-hand side, use "Add" to add the "Some Project" as a reference.
Doing so will ensure that ALL resources (maps, schemas, orchestrations, send ports, receive locations, rules, etc.) deployed for "Some Application" are available/referensible in "Some Other Application".
Regards.

BizTalk BTDF Custom Pipeline deployment

I have Schemas, Maps, Pipelines, Orchestration all under 1 BizTalk project A.
I have created another project B and have written custom c# Custom Pipeline component.
A and B are both under 1 solution.
I am using BTDF for deployment. Only for project 'A' I created the .btdf proj and mentioned :
<Itemgroup>
<schemas Include= "Corp.Integrations.ProjName.dll">
<LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath)
</schemas>
</ItemGroup>
Do I need to do add anything here ?
<IncludePipelines>False</IncludePipelines> ----> do I need to make it true ?
<ItemGroup>
<AppsToReferenceInclude="Corp.Integration.Proj"/>
<ItemGroup>
Please help, my Proj B is not deploying or inserting into GAC or under Custom Pipeline components.
MBH

Hello,
First, you need to GAC the Custom pipeline component dll.
And from Property Group you need to Include
<IncludePipelineComponents>true</IncludePipelineComponents>
From Item Group
<PipelineComponents Include="yourPipelineComponent.dll">
<LocationPath>..\$(ProjectName)\bin\</LocationPath>
</PipelineComponents>
Praj Dixit

Custom Pipeline for Biztalk Swift accelator

Hi Everyone,
am using BizTalk 2013R2, can any reply how to write custom pipeline for disassembler stage for swift accelater.
Thanks & Regards
Rajiv

Hi Rajiv,
I think we has already discussed your issue in previous post
https://social.msdn.microsoft.com/Forums/en-US/2df11643-51b8-4d58-9e83-5abcac590b22/custom-pipeline-code-for-swift-disassembler?forum=biztalkgeneral#2df11643-51b8-4d58-9e83-5abcac590b22
thanks
Abhishek

Custom pipeline component creates the folder name to archive messages

Hi
I have an requirement that a BizTalk application is receiving untyped messages and at the receive location the pipeline have to archive the incoming message with the specifications:
suppose I have an xml like
<PurchaseOrder>
<OrderId>1001</OrderId>
<OrderSource>XYZ</OrderSource>
<Code>O01</Code>
</PartyType>
In the pipeline component it has to read this xml and have to use OrderSource value 'XYZ' to create a archival folder and the message have to archive with file name '%MessageId%'
It has to be done by writing custom pipeline component where I am not familiar with c# coding, Can anyone please how to implement mechanism.
Thanks In Advance
Regards
Arun
ArunReddy

Hi Arun,
Use
BizTalk Server Pipeline Component Wizard to create a decode pipeline component for receive. Install this wizard. This shall help you to create the template project for your pipeline component stage.
Use the following code in the Execute method of the pipeline component code. This code archives the file based with name of the file name received.
public Microsoft.BizTalk.Message.Interop.IBaseMessage Execute(Microsoft.BizTalk.Component.Interop.IPipelineContext pc, Microsoft.BizTalk.Message.Interop.IBaseMessage inmsg)
MemoryStream tmpStream = new MemoryStream();
try
string strReceivedFilename = null;
DateTime d = DateTime.Now;
try
//Get the file name
strReceivedFilename = inmsg.Context.Read("ReceivedFileName", "http://schemas.microsoft.com/BizTalk/2003/file-properties").ToString();
if (strReceivedFilename.Contains("\\"))
strReceivedFilename = strReceivedFilename.Substring(strReceivedFilename.LastIndexOf("\\") + 1, strReceivedFilename.Length - strReceivedFilename.LastIndexOf("\\") - 1);
catch
strReceivedFilename = System.Guid.NewGuid().ToString();
originalStream = inmsg.BodyPart.GetOriginalDataStream();
int readCount;
byte[] buffer = new byte[1024];
// Copy the entire stream into a tmpStream, so that it can be seakable.
while ((readCount = originalStream.Read(buffer, 0, 1024)) > 0)
tmpStream.Write(buffer, 0, readCount);
tmpStream.Seek(0, SeekOrigin.Begin);
//ToDo for you..
//Access the receive message content using standard XPathReader to access values of OrderSource and construct file pathAccess the receive message content using standard XPathReader to acceess values of OrderSource and contruct the file path
string strFilePath = //Hold the value of the file path with the value of OrderSource
string strCurrentTime = d.ToString("HH_mm_ss.ffffff");
strFilePath += "\\" + strReceivedFilename + "_";
FileStream fileStream = null;
try
System.Threading.Thread.Sleep(1);
fileStream = new FileStream(strFilePath + strCurrentTime + ".dat", FileMode.CreateNew);
catch (System.IO.IOException e)
// Handle the exception, it must be 'File already exists error'
// Wait for 10ms, change the file name and try creating the file again
// If the second 'file create' also fails, it must be a genuine error, it'll be thrown to BTS engine
System.Threading.Thread.Sleep(10);
strCurrentTime = d.ToString("HH_mm_ss.ffffff"); // get current time again
string dtcurrentTime = DateTime.Now.ToString("yyyy-MM-ddHH_mm_ss.ffffff");
fileStream = new FileStream(strFilePath + strCurrentTime + ".dat", FileMode.CreateNew);
while ((readCount = tmpStream.Read(buffer, 0, 1024)) > 0)
fileStream.Write(buffer, 0, readCount);
if (fileStream != null)
fileStream.Close();
fileStream.Dispose();
if (originalStream.CanSeek)
originalStream.Seek(0, SeekOrigin.Begin);
else
ReadOnlySeekableStream seekableStream = new ReadOnlySeekableStream(originalStream);
seekableStream.Position = 0;
inmsg.BodyPart.Data = seekableStream;
tmpStream.Dispose();
catch (Exception ex)
System.Diagnostics.EventLog.WriteEntry("Archive Pipeline Error", string.Format("MessageArchiver failed: {0}", ex.Message));
finally
if (tmpStream != null)
tmpStream.Flush();
tmpStream.Close();
if (originalStream.CanSeek)
originalStream.Seek(0, SeekOrigin.Begin);
return inmsg;
In the above code, you have do a section of code which will access the receive message content using standard XPathReader to access values of OrderSource and construct the file path. I have
commented the place where you have to do the same. You can read the XPathReader about here..http://blogs.msdn.com/b/momalek/archive/2011/12/21/streamed-xpath-extraction-using-hidden-biztalk-class-xpathreader.aspx
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Deploying the custom Pipeline component in Production

I would like to know how to deploy the Pipeline component in to production. I created an an application in dev with the custom receive pipeline component in it. Thought importing the application's msi and binding file in production will automatically deploy
the pipeline component in to Pipeline component's folder. Bad thing is I didnt check if .dll was in Pipeline component's folder and ran the application. Now the messages got suspended with error
There was a failure executing the receive pipeline:Source: "Unknown " Receive Port: "" URI: "" Reason: Could not load file or assembly 'file:///E:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components\.dll' or
one of its dependencies. The system cannot find the file specified.
Help me out with this. Thanks

You do not need to copy the DLL in C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components.
You have to just GAC the dll on all the BizTalk servers and restart the host instance.
Please see
BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher wiki article
I hope this solves all your queries.
Greetings,HTH
Naushad Alam
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or
Mark As Answer
alamnaushad.wordpress.com

Unable to add the Custom Pipeline component in to the Visual Studio Tool Box

I have tried to create the custom Pipeline component to transfer the large message in Receive side,
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Xml;
using System.IO;
using Microsoft.BizTalk.Message.Interop;
using Microsoft.BizTalk.Component.Interop;
namespace Sample.LargeFilesDecoder
[ComponentCategory(CategoryTypes.CATID_PipelineComponent)]
[ComponentCategory(CategoryTypes.CATID_Encoder)]
[System.Runtime.InteropServices.Guid("25984614-BCFD-4c47-82FC-4A2300B76411")]
public class LargeFilesDecoder : IBaseComponent,
IComponentUI,
IComponent,
IPersistPropertyBag
#region IBaseComponent Members
public string Description
get
return "Pipeline component used to receive Larger Files through SFTP Ports";
public string Name
get
return "LargeFilesDecoder";
public string Version
get
return "1.0.0.0";
#endregion
#region IComponentUI Members
public IntPtr Icon
get
return new System.IntPtr();
public System.Collections.IEnumerator Validate(object projectSystem)
return null;
#endregion
#region IPersistPropertyBag Members
private string _largeFileLocation;
private int _thresholdSize;
public string LargeFileLocation
get { return _largeFileLocation; }
set { _largeFileLocation = value; }
public int ThresholdSize
get { return _thresholdSize; }
set { _thresholdSize = value; }
public void GetClassID(out Guid classID)
classID = new Guid("DBA77DFA-5D3E-4B85-8F78-1D6330B6BCA0");
public void InitNew()
public void Load(IPropertyBag propertyBag, int errorLog)
object val1 = null;
object val2 = null;
try
propertyBag.Read("LargeFileLocation", out val1, 0);
propertyBag.Read("ThresholdSize", out val2, 0);
catch (ArgumentException)
catch (Exception ex)
throw new ApplicationException("Error reading PropertyBag: " + ex.Message);
if (val1 != null)
_largeFileLocation = (string)val1;
if (val2 != null)
_thresholdSize = (int)val2;
public void Save(IPropertyBag propertyBag, bool clearDirty, bool saveAllProperties)
object val1 = (object)_largeFileLocation;
propertyBag.Write("LargeFileLocation", ref val1);
object val2 = (object)_thresholdSize;
propertyBag.Write("ThresholdSize", ref val2);
#endregion
#region IComponent Member
public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage pInMsg)
if (_largeFileLocation == null || _largeFileLocation.Length == 0)
_largeFileLocation = Path.GetTempPath();
if (_thresholdSize == null || _thresholdSize == 0)
_thresholdSize = 4096;
if (pInMsg.BodyPart.GetOriginalDataStream().Length > _thresholdSize)
Stream originalStream = pInMsg.BodyPart.GetOriginalDataStream();
string largeFilePath = _largeFileLocation + pInMsg.MessageID.ToString() + ".msg";
FileStream fs = new FileStream(largeFilePath, FileMode.Create);
// Write message to disk
byte[] buffer = new byte[1];
int bytesRead = originalStream.Read(buffer, 0, buffer.Length);
while (bytesRead != 0)
fs.Flush();
fs.Write(buffer, 0, buffer.Length);
bytesRead = originalStream.Read(buffer, 0, buffer.Length);
fs.Flush();
fs.Close();
// Create a small xml file
string xmlInfo = "<MsgInfo xmlns='http://Sample.LargeFilesDecoder'><LargeFilePath>" + largeFilePath + "</LargeFilePath></MsgInfo>";
byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(xmlInfo);
MemoryStream ms = new MemoryStream(byteArray);
pInMsg.BodyPart.Data = ms;
return pInMsg;
#endregion
I have
Added .dll file in to the Global Assembly Cache (use gacutil)
Copied it the Pipeline Components folder (E:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components)
Everything was successful, when I try to add the component to the Toolbox I get the message like below and cannot find the component in Toolbox.
Tried several times but still getting stuck in the same place. I am using Visual Studio 2013. Any help is greatly appreciated.

Do not put the Assembly in the %\Pipeline Components folder. Pipeline Component Assemblies should be in the GAC only.
To correctly deploy a custom Pipeline Component, you can follow the steps in this Wiki Article:
http://social.technet.microsoft.com/wiki/contents/articles/26404.biztalk-deploying-custom-pipeline-components-in-biztalk-server-2006-and-higher.aspx
I have never seen that specific error before. Are you sure you're browsing from the Pipeline Components tab?

ESB - Is there a way to set context properties when using esb custom pipeline

Hi there,
I have a situation where I am using a oneway wcf sql custom receive adapter to polling db and a two-way solicit response wcf sql send adapter to update the db and receive a result back.
Now I had got this working by setting the BTS.Operation and BTS.MessageType properties using a custom receive pipeline on the receive port. FOR SOME REASON THESE TWO WERE NOT SET BY THE RECEIVE PORT !!!
Now I have decided to wrap all that in en ESB itinerary by converting the send port into a dynamic one. I get the following error:
Exception of type 'Microsoft.BizTalk.Message.Interop.BTSException' was thrown.
Since I am using the ESB pipeleine - ItineraryReceiveXML I am not able to set the BTS.Operation and BTS.MessageType explicitly in a pipeline neither can I derive a pipeline form the ESB pipeline as it's a sealed class.
So my questions are:
1. Any idea what the above error could be ?
2. Also is there a way I get set context properties using an ESB itinerary as that is the only difference from before, can I do that in a map ?
Thanks
Phanindra

BTS.MessageType is typically set by one of the Disassemblers.
BTS.Operation has nothing to do with the Receive Port/Location and is set by the Engine only when coming from an Orchestration Port.
But, you can set any Property in any Stage with a custom Pipeline Component as you've found.
"Exception of type 'Microsoft.BizTalk.Message.Interop.BTSException' was thrown."
There's usually a lot more to the stack trace. You'll have to include the whole thing.
Finally, what benefit do you expect from adding the ESB layer? This is pretty trivial with an Orchestration.

Custom Pipeline Component - Deployment Issue

We have created a custom pipeline component that logs information via ETW. The component was added to a suite of common pipelines that our applications share, as well as to a handful of application specific pipelines that require other custom components
used only by those applications. I made a change to the component and deployed the DLL to our test environment, added it to the GAC and restarted all of the host instances. The common pipelines all seem to work fine with the new DLL, but for some reason those
pipelines that are application specific (which use the same version of the DLL) all started generating the "Object reference not set to an instance of the object" error. So I replaced the new DLL with the original version and all of the pipelines
(common and otherwise) worked okay again. Can anyone tell me what I need to do to get the application specific pipelines to work with the modified DLL?
Thank you.
Thanks, Bruce

Quite certain. The application specific pipelines call public methods that write string data to a log file - they don't pass any parameters - all of that is contained within the component itself. We only changed the content of the data for the internal parameters,
not the data type, so the signature of the procedures remain the same.
The original author of the code had the component logging every attribute of the pipeline and received message to the log file which was creating very large and non-useful logs. We only replaced the call to the pc.GetProperties() and inmsg.GetProperties()
methods (both return string values) with concise strings containing the data we need logged.
The first version of the pipeline did not contain the GetProperties methods, those were added later and the pipeline was deployed for testing. At that time, all of the application specific pipelines began generating errors that the GetProperties() method
was not recognized, so we ended up having to go back and rebuild and re-deploy all of the application specific pipelines to use the newer version in order to get them to work. We should not have to go through this much effort to replace a shared
library, and am hoping we can find a way to deploy it without having to redeploy all of the other pipelines as well.
We deployed the new pipeline according to Microsoft's recommendations in
BizTalk: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher so we are left scratching our heads at this point.
Thanks, Bruce

Biztalk Custom Pipeline Error

Similar Messages

Maybe you are looking for