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.

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 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.

  • 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.

  • TS3694 What to do when you recive an error message 9006?

    What to do when you recive an error message 9006?

    You came from the correct article. Here is what it has to say about that error.
    Error 2, 4 (or -4), 6, 1000, 9006
    Follow the steps to troubleshoot security software. Often, uninstalling third-party security software will resolve these errors.
    There may be third-party software that modifies your default packet size in Windows by inserting a TcpWindowSize entry into your registry. An incorrectly set default packet size can cause these errors. Contact the manufacturer of the software that installed the packet size modification for assistance or follow this article by Microsoft: How to reset Internet Protocol (TCP/IP).
    Verify that access to ports 80 and 443 are allowed on your network.
    Verify that communication to albert.apple.com or phobos.apple.com isn't blocked by a firewall or other Internet security setting.
    Discard the .ipsw file, open iTunes and attempt to download the update again. See the steps under "Advanced steps > Rename, move, or delete the iOS software file (.ipsw)" below for file locations.
    Restore your device while connected to a different network.
    Restore using a different computer.

  • Pipeline Error: -2147475455

    NI Update Service is not working. Usualy "no internet" error message. Here is the log:
    [2014-11-03 16:13:57.254] ----------------------------------------------------------------------
    [2014-11-03 16:13:57.294] National Instruments Update Service
    [2014-11-03 16:13:57.294] ----------------------------------------------------------------------
    [2014-11-03 16:13:57.294] Command-line: NIUpdateService.exe -log d:\temp\log20141103.txt
    [2014-11-03 16:13:57.294] Version: 14.0.0.59
    [2014-11-03 16:13:57.294] User locale: vi-VN 1066
    [2014-11-03 16:13:57.294] Update Service language: en-XX
    [2014-11-03 16:13:57.294] Elevated: False
    [2014-11-03 16:13:57.394] UpdateServiceStarterPresenter.CheckPrimaryInstance: This is the primary instance.
    [2014-11-03 16:13:57.404] NiLmCLientApi.NiLmClientDLL: DLL loaded successfully.
    [2014-11-03 16:13:57.454] NiLmClientApi.CloseNiLm: NiLmClient DLL unloaded successfully.
    [2014-11-03 16:13:57.454] License Manager: Update Service is enabled.
    [2014-11-03 16:13:58.744] UpdateServicePresenter.CheckForUpdatesPressed: Begin
    [2014-11-03 16:13:58.744] UpdateServicePresenter.CheckForAndEvaluateUpdates: Beginning the process of checking for and evaluating updates.
    [2014-11-03 16:14:01.218] Pipeline is up.
    [2014-11-03 16:14:01.218] Finished worker thread Ping Pipeline.
    [2014-11-03 16:14:01.218] Starting worker thread Collect Information.
    [2014-11-03 16:14:01.218] UpdateServicePresenter.CollectInformation: Collecting system information.
    [2014-11-03 16:14:01.282] DeviceFinder.DeviceFinder: SystemAPI version is 5.5.0 or later. Assembly can be loaded. (Version=14.0.0)
    [2014-11-03 16:14:09.344] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:09.344] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:09.344] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:09.354] Finished worker thread Collect Information.
    [2014-11-03 16:14:09.354] Starting worker thread Check For Updates.
    [2014-11-03 16:14:09.354] UpdateServicePresenter.CheckForUpdates: Querying ni.com for Critical updates.
    [2014-11-03 16:14:09.354] Plugins.Base.Plugin.DownloadCatalog: Calling SubmitAndMonitorQuery
    [2014-11-03 16:14:12.674]
    [2014-11-03 16:14:12.674] ***ERROR: Plugins.Base.Plugin:DownloadCatalog: Exception querying for updates Exception information: NI.UpdateService.Common.UpdateServiceException: Pipeline Error: -2147475455
    at NI.UpdateService.Common.PipelineBase.ThrowResult(Int32 returnValue)
    at NI.UpdateService.Common.PipelineBase.IsQueryFinished(Int32 returnValue)
    at NI.UpdateService.Common.PipelineBase.QueryCheck(UInt32 wait)
    at NI.UpdateService.Plugins.Base.Plugin.SubmitAndMonitorQuery(OptionsUpdateSearchType searchType, Boolean& canceled)
    at NI.UpdateService.Plugins.Base.Plugin.DownloadCatalog(OptionsUpdateSearchType searchType, Boolean& canceled)
    [2014-11-03 16:14:12.674]
    [2014-11-03 16:14:12.674] Plugins.Base.Plugin.DownloadCatalog: End
    [2014-11-03 16:14:12.674] Finished worker thread Check For Updates.
    [2014-11-03 16:14:12.674]
    [2014-11-03 16:14:12.674] ***ERROR: UpdateServicePresenter.WorkerSequence.WorkerFinished: Exception thrown in worker thread Check For Updates Exception information: NI.UpdateService.Common.UpdateServiceException: Checking for Critical updates failed
    [2014-11-03 16:14:12.674]
    [2014-11-03 16:14:37.754] UpdateServicePresenter.BeforeClose: Determine whether to prompt to confirm.
    [2014-11-03 16:14:37.754] UpdateServicePresenter.StopWorkers: Stopping workers
    [2014-11-03 16:14:37.754] UpdateServicePresenter.StopWorkers: complete.
    [2014-11-03 16:14:37.754] Not downloading. Continue closing.
    [2014-11-03 16:14:40.364] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:40.364] calling WsUdClose 1
    [2014-11-03 16:14:40.364] done - setting pipelineId=0
    [2014-11-03 16:14:40.364] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:40.364] calling WsUdClose 2
    [2014-11-03 16:14:40.364] done - setting pipelineId=0
    [2014-11-03 16:14:40.364] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:40.364] calling WsUdClose 3
    [2014-11-03 16:14:40.364] done - setting pipelineId=0
    [2014-11-03 16:14:40.364] WebPipeline.ResetPipeline: Begin
    [2014-11-03 16:14:40.364] calling WsUdClose 4
    [2014-11-03 16:14:40.364] done - setting pipelineId=0
    [2014-11-03 16:14:40.374] GlobalMutex.Release: Mutex '_NIMetaInstallerMutex' is being released.
    [2014-11-03 16:14:40.374] GlobalMutex.AcquireMutex: Mutex thread is now releasing mutex '_NIMetaInstallerMutex'.
    [2014-11-03 16:14:40.374] ----------------------------------------------------------------------

    Hello and sorry for late reply.
    Here is the error message:
    It apears about 1 second after this is displayed:
    I have tried on 3 different networks (including unrestricted home network). The windows firewall is disabled. I'm using win7 64 bits

  • BizTalk EDI pipeline not failing due to NTE^02 exceeding 80 characters

    Hi,
     I have a case where special characters are used in the free form description that is placed in an NTE^02 segment in an outbound EDI document. The maximum length allowed for NTE^02 is 80 characters. But if a special character (Europe) is in the text,
    it is supposed to be counted as 2 characters not 1. This is not being caught by the BizTalk EDI pipeline and file is failing EDI validation on the partners side due to this. 
    Any ideas if this is a bug or I am not setting a configuration?
    Thanks!

    Then you need to check their Companion Guide, or ask them, exactly what character set they're expecting.
    If they say
    "SóME TEXT" is 10 characters, then they are likely expecting Basic, or maybe Extended which is single
    byte encoding (it's just ASCII), but you are sending UTF8.  "ó" is a valid Extended single byte character but in UTF8 would be double-byte.
    X12 supports UTF8 so double-byte characters are allowed, provided both sides agree.
    Whatever the correct value, the better place to set it would be in the Agreement.
    Thanks. I'll it out.
    The partner is using UTF-8 which is what i am setting (and default). So does that mean "ó" is correctly being seen by the partner as occupying 2 characters lengths?

  • BizTalk Receive Pipelines

    Hi Experts,
    I'm a starter in BizTalk......and I have a question on BizTalk Receive Pipelines.
    Here is the Scenario. We had an existing File Receive Location . It was associated with an existing Custom Receive Pipeline. I deleted the Receive Location and am trying to recreate it exactly with the same attributes. While recreating this, I’m trying to
    choose from a Custom Receive Pipeline, but I cannot see any of the Custom Receive Pipelines in the dropdown list. All I can see are the default Receive Pipelines in the dropdown list . I can,  however see the Custom Pipeline (including the one I would
    like to select) in the ‘Pipelines’ folder when I click on it.
    Any help on this would be greatly appreciated.
    Kind Regards,  Suchi
    <v:shape alt="" id="Picture_x0020_1" o:spid="_x0000_i1025" style="width:960pt;height:10in;" type="#_x0000_t75"><v:imagedata o:href="cid:[email protected]"
    src="file:///C:\Users\SE791~1.SAM\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png">
    </v:imagedata></v:shape>

    Hi Suchi,
    All the BizTalk Applications by default reference the "BizTalk.System" Application and this is why you can see the default Receive Pipelines from the Drop-down list (XMLReceive or PassThruReceive). However "BizTalk.System" Application is an internal application
    witch means that is read-only so it can't be changed or updated by you.
    In you case, and as Morten la Cour already referenced, you need to make sure if the
    custom receive pipeline is deployed to the same Application where you are trying to create the File Receive Location... otherwise
    you need to reference the application that contains the Custom Pipeline in the current application that you are trying to create the port
    or move the artifact (custom pipeline) to the current application that you are trying to create the port, in this case only if the pipeline is not used by any other port.
    To add a reference to another application check:
    How to Add a Reference to Another Application
    Sandro Pereira
    DevScope | MVP & MCTS BizTalk Server 2010
    http://sandroaspbiztalkblog.wordpress.com/ |
    @sandro_asp
    Oporto BizTalk Innovation Day | 14th March 2013 – Oporto, Portugal
    Please mark as answered if this answers your question.

  • Biztalk Custom Send Pipeline Error

    Hello Experts,
    I have been trying to work with the Custom Send Pipeline, which picks up the .xml file which has the path directory of the file needs to be sent to the destination. I used the code from 
    here to practice how it works
    using System;
    using System.Collections.Generic;
    using System.Text;
    using Microsoft.BizTalk.Message.Interop;
    using Microsoft.BizTalk.Component.Interop;
    using System.IO;
    namespace Sample.SndLargeFiles
    [ComponentCategory(CategoryTypes.CATID_PipelineComponent)]
    [ComponentCategory(CategoryTypes.CATID_Encoder)]
    [System.Runtime.InteropServices.Guid("52dcc4e5-28e1-49a2-81fd-de496ac80fe8")]
    public class SampleSndLargeFiles : IBaseComponent, IComponentUI, IComponent
    #region IBaseComponent Members
    public string Description
    get
    return "Send Large Files to destination reading from disk";
    public string Name
    get
    return "SampleSndLargeFiles";
    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 IComponent Members
    public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage pInMsg)
    // Read filepath from the context properties
    string largeFilePath = pInMsg.Context.Read("LargeFilePath", "https://SamplePL.PropertySchema").ToString();
    // Read file from disk
    int bufferSize = 1024;
    FileStream fs = new FileStream(largeFilePath, FileMode.Open, FileAccess.Read, FileShare.Read, bufferSize);
    if (fs.CanSeek)
    fs.Position = 0;
    pInMsg.BodyPart.Data = fs;
    return pInMsg;
    #endregion
    I am getting error when I am trying to use in my send Port
    "Reason: Object reference not set to an instance of an object.  "
    I have checked GAC and restarted the host instances after deploying the pipeline but nothing helps.Any help is greatly appreciated.Thanks

    Johns,
    If I debug the orginal code it shows
    "An exception of type 'System.NullReferenceException' occurred in Jax.Dhana.SndLargeFiles.dll but was not handled in user code
    Additional information: Object reference not set to an instance of an object."
    in the below line
    string largeFilePath = pInMsg.Context.Read("LargeFilePath", "https://SamplePL.PropertySchema").ToString()
    If I change the code to
    string largeFilePath = System.String.Empty;
    object propVal = pInMsg.Context.Read("LargeFilePath", "https://SamplePL.PropertySchema");
    if (propVal != null) {
    largeFilePath = (System.String) propVal;
    I am seeing "Empty path name is not legal" on the below line,
    FileStream fs = new FileStream(largeFilePath, FileMode.Open, FileAccess.Read, FileShare.Read, bufferSize);

  • Biztalk AS2 encryption error for file bigger than 100MB

    I am getting following error when I am trying to receive file bigger than 100 MB. I was getting same error when I was trying file bigger than 5MB and I applied windows CU5. Now I can receive big file (I tested till 60 MB). New file which is coming is 110MB
    and we start getting this error. 
    Can somebody help me to figure out this issue.
    I am using Biztalk 2010 with windows 2008 server
    A message received by adapter "HTTP" on receive location "RecLocAS2All" with URI "/xxxxxx/BTSHTTPReceive.dll" is suspended. 
     Error details: An output message of the component "Microsoft.BizTalk.EdiInt.PipelineComponents" in receive pipeline "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Receive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral,
    PublicKeyToken=31bf3856ad364e35" is suspended due to the following error: 
         An error occurred when decrypting an AS2 message..
     The sequence number of the suspended message is 2.  

    I tried passthrough pipeline and I can receive encrypted file.Now trying to write code to decrypt it but I can not. Based on certificate I can say it is RSASHAI, so using it for decrypt. But getting error at  Convert.FromBase64String(text) where text
    is encrypted test from file.
    I am getting following error 
    The input is not a valid Base-64 string as it contains a non-base 64 character,
    more than two padding characters, or an illegal character among the padding characters.
    Can somebody help me to understand it and resolve this. Mean time trying
    to convene customer for compressed file .Please help me to understand above error. 

  • Biztalk Internal Server Error

    Hi
    I am experiencing an error when sending an IDOC message to SAP from BizTalk. The IDOC reaches SAP with no issues however we do not receive the standard GUID response message back and this error is reported by BizTalk - 
    Error Description: An internal server error was encountered while attempting to transmit the message
    We are using the WCF-Custom adapter.
    Has anyone encountered this before?
    Thanks in advance
    Riaz

    One rule of thumb I have been following (and suggested by my sap guys) while working with SAP is always take the latest version of Idoc. If I understood you correctly, your SAP guys updated the Idoc version in QA but you haven't replaced new version of Idoc
    with new version. If this is the case, then you will ultimately gonna have same issue in production when SAP people update the production system. Your WCF adapter is not complaining because it matches the deployed schema with the message you are attempting
    to send. Also SAP doesn't return error to BizTalk normally when you send old version of IDOC and they can't process it correctly. 
    Additionally, in my case I have been practicing Oneway port when I don't care about the GUID, and have no issue too.
    I am not clear why you are able to see response when you change pipeline to passthrough though. I have noticed when there is passthrough my wcf sap adapter is not able to deal with the response and complains "received unexpected message etc..".
    If you verified both Send and SendResponse schemas are not changed from visual studio then I would verify (just to be 100%) this from BizTalk admin console too (http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/mymessage#Send and http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/mymessage#SendResponse).
    Another test practice that works for me is, I try to send just a valid IDOC instance using filedrop method and subscribing that message towards sap port and subscribe response message based on messagetype too. (Provided schema is already deployed). If this
    doesn't work I will surely consider replacing new schema version  and deploy it again and then test.
    Please mark it as Answer if this answers your question
    Thanks.
    Mo
    The contents I write here is my personal views, not the view of my employer and anyone else.

  • BizTalk Runtime configuration error - "Creation of Adapter FILE Configuration Store entries failed"

    Hi,
    I am trying to install Biztalk Server 2006 R2 on a Vista Ultimate
    edition machine. I completed the installation successfully, and have
    configured "Enterprise SSO" and "Group" features. I am getting the
    following error while configuring the BizTalk Runtime feature.
    "Creation of Adapter FILE Configuration Store entries failed.
    The SSO system is currently disabled."
    I have already done/tried the following:
    1. I tried different settings - Inprocess only, Inprocess and
    isolated, each trusted, each with a regular user account and each with
    an administrator user account. In all cases I get the same error.
    2. I have made the changes suggested here (related to rpc
    authentication changes after Windows XP SP2) but it still doesnt
    change anything: http://blogs.msdn.com/scottwoo/archive/2004/05/19/135453.aspx
    Any suggestions?
    Thanks in advance,
    Anand

    I'm having a similar installation error on an XP SP2 box and was getting the same error message (Creation of Adapter FILE Configuration Store entries failed. The SSO system is currently disabled.).  I checked and the Enterprise SSO application is not appearing in the list of services, and doing a command line "net start ENTSSO" returns an invalid service error.
    So going on the theory that SSO did not install correctly and get registered as a server, I went ahead and uninstalled BizTalk/SSO, blew away BTS/SSO databases, and tried to reinstall (selected all options for install).
    After BizTalk installed, I entered a local admin account and chose "Custom" installation.  Because the error message pointed at an SSO problem, I tried to apply the SSO configuration ONLY, using the default SSO Administrator/Affiliate Administrator accounts with the default admin account, but it keeps failiing at the same point in the install log when it tries to start SSO (see log below).
    [10:30:51 AM Info ConfigHelper]  Creating service: ENTSSO, start type: 2, exe: "C:\Program Files\Common Files\Enterprise Single Sign-On\ENTSSO.exe", dependencies: RPCSS,COMSysApp,MSSQLSERVER, account: .\bizservice
    [10:30:51 AM Info ConfigHelper] bizservice is a local entity.
    [10:30:52 AM Info ConfigHelper]  Created service: ENTSSO
    [10:30:52 AM Info SSOServerCfg] (ssoconfigobj2.cpp:7370) CSSOServerCfg::ConfigureSCP
    [10:30:52 AM Info SSOServerCfg] (ssoconfigobj2.cpp:7445) NetScheduleJobAdd: nRc = 00000000, dwJobId = 1
    [10:30:52 AM Info SSOServerCfg] (ssoconfigobj2.cpp:5697) CSSOServerCfg:tartService
    [10:30:52 AM Info SSOServerCfg] (ssoconfigobj2.cpp:5721) The SSO service is starting.
    [10:30:52 AM Info SSOServerCfg] (ssoconfigobj2.cpp:5852) ENTER: CSSOServerCfg::WaitServiceState
    [10:30:52 AM Info SSOServerCfg] (ssoconfigobj2.cpp:5892) The SSO service state is: The service is starting (SERVICE_START_PENDING)
    [10:30:53 AM Info SSOServerCfg] (ssoconfigobj2.cpp:5892) The SSO service state is: The service is not running (SERVICE_STOPPED)
    The SSO database does get created, but the SSO Administrators and SSO Affiliate Administrators local groups do not.
    So my theory here is that for some reason SSO cannot start, the exception is caught and the app rolls back.
    Any ideas?

  • Pipeline error for abap proxy to IDoc scenario

    hi experts,
    i am getting the following system error in moni for my proxy to idoc scenario.
    In error it shows :
    "Receiver service cannot be converted into an ALE logical system"
    but i have checked adapter specific attributes of both receiver
    and sender sys and they both have logical systems ( SO this is not the problem)
    TRACE
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
    pls suggest .
    Appropriate points will be awarded

    Hi,
    Copy the payload from moni and test the mapping.
    The error may be due to XML file generated by sender channel is not proper.
    and also look at this blog
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Please reward points if it helps
    Thanks
    Vikranth

  • BizTalk Send Port Error

    We are getting error on send port after some changes in the map, but there is no change in the map which is throwing error -
    Event Type: Error
    Event Source: BizTalk Server 2009
    Event Category: (1)
    Event ID: 5754
    Date:  11/26/2013
    Time:  1:14:22 PM
    User:  N/A
    Computer: XXXX
    Description:
    A message sent to adapter "WCF-Custom" on send port "SndABCD" with URI "mssql://ABCDSQLDB/INSTANCE/ABCDReport?" is suspended.
     Error details: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
     MessageId:  {A79F62AD-3C63-4543-9FEF-2682CF83106A}
     InstanceID: {941EBEF7-7008-451C-AEBE-C7407462F943}
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    I have checked below links already which suggest, gac the DLL, but did not work for me -->
    http://social.msdn.microsoft.com/Forums/en-US/01791899-a0bf-451d-9004-fe8b696a9270/custom-functoid-the-system-cannot-find-the-file-specified?forum=biztalkediandas2
    http://blogs.eliasen.dk/Technical/post/2010/01/17/TheSystemCannotFindTheFileSpecified.aspx
    http://stevestechnotes.blogspot.com/2008_02_01_archive.html

  • File to file reciver interface error

    Hi,
    In our production XI system. I have file to file scenerio in which I am sending file from SAP to non SAP system.
    While monitoring in runtime workbench in message monitoring I got an error in adapter engine and in the reciver communication channel:
    2010-07-13 16:19:09 Error Attempt to process file failed with com.sap.aii.adapter.file.ftp.FTPEx: 553 SAPLGCINPFFSSET20100713155105.TXT: Permission denied.
    2010-07-13 16:19:09 Error Exception caught by adapter framework: SAPLGCINPFFSSET20100713155105.TXT: Permission denied.
    2010-07-13 16:19:09 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SAPLGCINPFFSSET20100713155105.TXT: Permission denied.: com.sap.aii.adapter.file.ftp.FTPEx: 553 SAPLGCINPFFSSET20100713155105.TXT: Permission denied..
    Please tell me the solution. This production move is really important.
    Thanks and regards,
    Lokesh

    Check whether FTP user which is used in File adapter has Read/Write/Delete permission on the file or FTp folder.
    also check this faq for 553 permission denied FTP error- http://faq.realcart.com/error553-.html -
    chirag
    Edited by: Chirag Gohil on Jul 13, 2010 6:43 PM

Maybe you are looking for