Biztalk Receive pipeline doesnot start

All.
Suddenly my Biztalk server application doesnt pick data from db.(pooilng interval =3 Sec). I checked in tracked service instance but no instance reated.
And all the other existing applicaion received Routing failure exception.
Please advice what needs to be done soon. Thanks in advance.

Hi 
Thanks for you response. I found the issue. Suddenly DB was down and so the i didnt receive any data from the receive location into orchestration. But there was no error regarding this in biztalk side. i hope some error should be thrown from biztalk if db
is down or some connection problem with DB.

Similar Messages

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

  • Receive pipeline issue in BizTalk

    Hi All,
    I'm getting below error frequently in BizTalk while the records triggering from inbound to out bound.
    Here Inbound transport Type : FILE  and Outbound transport Type :
    WCF-BasicHttp
    Log Name:      Application
    Source:        BizTalk Server
    Date:          18/2/2015 12:38:53 PM
    Event ID:      5719
    Task Category: BizTalk Server
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      someserver.local
    Description:
    There was a failure executing the receive pipeline: " BizTalk.Pipeline.ReceiveMeasureCSVs, SLNG.BizTalk.Pipeline, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bb4520a982c06a31" Source: "ESB Dispatcher" Receive Port: "SLNG_DynamicResolutionOneWay"somelocation
    _*.csv" Reason: Root element is missing.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="BizTalk Server" />
        <EventID Qualifiers="49344">5719</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-02-18T04:38:53.000000000Z" />
        <EventRecordID>2022354</EventRecordID>
        <Channel>Application</Channel>
        <Computer>someserver.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data> BizTalk.Pipeline.ReceiveMeasureCSVs, SLNG.BizTalk.Pipeline, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bb4520a982c06a31</Data>
        <Data>ESB Dispatcher</Data>
        <Data>SLNG_DynamicResolutionOneWay</Data>
        <Data>\\sftp server location_*.csv</Data>
        <Data>Root element is missing.</Data>
      </EventData>
    </Event>
    How can i fix this error. Could you please assist me on this.
    Thanks in advance.
    Best Regards,
    Vasu

    Hi,
    Check the output of the map creating the msg to be sent to the port.
    https://social.msdn.microsoft.com/Forums/en-US/19ae19f2-1799-4b2a-a056-1619a955fa19/issue-with-publishing-schema-as-webservice-using-wcfbasichttp-two-way-channel?forum=biztalkgeneral#3492ac06-708a-4b3c-a594-e249fcfa57e3
    Regards Pushpendra K Singh

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

  • Issue with custom receive Pipeline component

    I have been facing issue with creating a custom receive pipeline component. The Pipeline is to receive large file, if the file size is large it has to read the incoming stream to a folder and pass only some meta data through the MessageBox. The Execute method
    I am using is,
    #region IComponent Members
    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() + ".zip";
    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 = "<ns0:MsgInfo xmlns:ns0='http://SampleTestPL.SchemaLocation'><LargeFilePath>" + largeFilePath + "</LargeFilePath></ns0:MsgInfo>";
    byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(xmlInfo);
    MemoryStream ms = new MemoryStream(byteArray);
    pInMsg.BodyPart.Data = ms;
    return pInMsg;
    #endregion
    Here I want the xml to be dropped in to the File share Eg: E:\Dropbox\PL\send and and the entire message to be dropped in the folder Eg: E:\Dropbox\sendLarge. so in the ReceivePipeline properties i set like
    And in the send port the destination i give is E:\Dropbox\PL\send.
    The issue is both the xml and the message are getting dropped in to the same folder E:\Dropbox\PL\send and the message is not getting dropped in E:\Dropbox\SendLarge. Any help is greatly appreciated.

    using System;
    using System.Collections.Generic;
    using System.Text;
    using Microsoft.BizTalk.Message.Interop;
    using Microsoft.BizTalk.Component.Interop;
    using System.IO;
    namespace Sample.ReceivePipelineLargeFile
    [ComponentCategory(CategoryTypes.CATID_PipelineComponent)]
    [ComponentCategory(CategoryTypes.CATID_Decoder)]
    [System.Runtime.InteropServices.Guid("53fd04d5-8337-42c2-99eb-32ac96d1105a")]
    public class ReceivePipelineLargeFile : IBaseComponent,
    IComponentUI,
    IComponent,
    IPersistPropertyBag
    #region IBaseComponent Members
    public string Description
    get
    return "Pipeline component used to receive large file and save it ina disk";
    public string Name
    get
    return "ReceivePipelineLargeFile";
    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("B261C9C2-4143-42A7-95E2-0B5C0D1F9228");
    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 Members
    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() + ".zip";
    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 = "<ns0:MsgInfo xmlns:ns0='http://SampleTestPL.SchemaLocation'><LargeFilePath>" + largeFilePath + "</LargeFilePath></ns0:MsgInfo>";
    byte[] byteArray = System.Text.Encoding.UTF8.GetBytes(xmlInfo);
    MemoryStream ms = new MemoryStream(byteArray);
    pInMsg.BodyPart.Data = ms;
    return pInMsg;
    #endregion
    Thanks Osman Hawari, for trying to help me out.

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

  • Encrypt xml message in receive pipeline

    Hi,
       I am new to biztalk .
       I have a requirement where i need to encrypt the xml message in the receive pipeline.I know i have to develop a custom pipeline component to do this but i don't know in which stage of receive pipeline should i place this component in?  
    please advice .
    Thanks in advance 

    Hi Rose,
    To decrypt the message in receive pipeline and you will place the custom pipeline component in Decode stage
    of the receive pipeline and encryption will be done at send pipeline and you will place the custom pipeline component in Encode stage of the send pipeline.
    Decryption at receive pipeline:
    Encryption at
    send pipeline:
    BizTalk
    Server 2013: Encrypting and Decrypting a Message
    You can also refer the MSDN articles on how to decrypt and
    encrypt message in BizTalk.
    How to Configure BizTalk Server for Receiving Encrypted Messages
    How to Configure BizTalk Server for Sending Encrypted Messages
    Rachit
    Please mark as answer or vote as helpful if my reply does

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

  • IBaseMessage.Context getting disposed for large message processing (There was a failure executing the receive pipeline: Reason: Cannot access a disposed object. Object name: 'MessageContext'.

    Hi,
    I am trying to parse a large message (2.7 MB file) in a custom Flat file Disassembler (inherited from the Microsoft.BizTalk.Component.FFDasmComp) this does exactly the same work for FFDasmComp but also promotes the count of disassembled messsages. This
    works fine for small messages but for large messages I get this error
    There was a failure executing the receive pipeline: "<pipeline name>, <Pipeline assembly>" Source: "Custom FlatFile Disassembler" Receive Port: "ReceivePort7" URI: "<the input file location>" Reason: Cannot access a disposed object.
    Object name: 'MessageContext'.
    In the event log
    what I am doing inside the custom flat file assembly is, I am saving all the disassembled messages in a List<IBaseMessage> and then finally when GetNext() method returns null I am promoting the nRecordCount in the messageContext of all the disassembled
    messages. This is where I get the error when trying to promote to the message context.(Cannot access a disposed object, Object name: 'MessageContext'). I think the messagecontext is getting disposed, but it should not as I still hold its reference in
    the List<IBaseMEssage);
    private long nRecordCount = 0;
    private List<IBaseMessage> oDisassembledMessages = new List<IBaseMessage>();
    Any idea why this happens ?
    Thanks in advance, PLEASE HELP
    Surya

    Hi Surya,
    Are you still facing this issue? and are you using Flat File Disassembler in your Receive pipeline?
    If yes then set 'RecoverableInterchangeProcessing' to True.
    Please have a look in below articles-
    BizTalk
    Pipeline - Flat File Disassembler Cannot Access a Disposed Object 'DataReader'
    biztalk-esb-toolkitflat-file-debatching
    BizTalk
    Server: List of Errors and Warnings, Causes, and Solutions
    This issue can also occur if you are using Large Size message, in this case you will have to optimize your code.
    Thanks,
    Prashant
    Please mark this post accordingly if it answers your query or is helpful.

  • Biztalk Receiving Duplicate Message

    How Do you avoid receiving a duplicate message?
    Christiane

    Hi Christiane,
    To “avoid” receiving duplicate message in BizTalk, only solutions is to avoid configure BizTalk receive location to the source system which sends the duplicate message.
    But you can “Reject” (or stop processing further) the received duplicate message in BizTalk.
    BizTalk would receive all the recognised messages from the configured source system. Defining a message as DUPLICATE or not is a custom business condition/requirement. This custom business condition/requirement
    various to various integration. Hence its not part of the BizTalk by default. You have to handle this business condition/requirement in BizTalk.
    If you don’t want the duplicate message to be published into messagebox or proceed further in BizTalk, you can consider using a custom receive pipeline component where you can implement a logic
    to check wheather the received message is duplicate or not.
    For example, if you receive a Order message and if OrderID definies the uniqueness of an order, then in custom receive pipeline once you received the message, access its OrderID and check it against
    a custom database to see if this OrderID is present in the db already or not. If the OrderID is not present in DB, then insert the OrderID in DB (for subsequent checks) and proceed the message furture. If the OrderID is already present in the db (then the
    received order is duplicate), then suspend (or don’t publish the received message furture) the message.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

  • Passing to multiple receive pipelines.

    Hello,
    I am rather new to BizTalk and have a design question.  Currently we are receive a custom receive pipeline in a receive port with multiple receive locations.  What I would like to do
    is pass a given message (these are HL7 messages coming in through the MLLP adapter) to both the current receive pipeline and another receive pipeline?  Is this possible?  If so how would I go about doing this?  I have thought about using an
    orchestration to call the receive pipelines but at this point the message is already in XML.  I need the native HL7 message to be passed through both pipelines.
    Thanks.
    -Chas

    Why do you want to do by passing same message to multiple pipelines.You associate a receive pipeline to a receive location not to a receive port.
    If you want to do two different process to the received native message, you can think about creating a custom receive pipeline with various component in different stages to process the native message before it being converted to XML.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

  • The wrong name of the message sender appears. The phone also does not notify the receiver. This started after we purchased in iPad and attempted sending that phone an iMessage.

    When sending messages to one of our iPhones, the wrong name of the sender appears. The phone also does not notify the receiver. This started after we purchased in iPad and attempted sending that phone an iMessage.

    Hi buddy, I figured out what is wrong with that. I had the very same issue, while sending an sms via iMessage on Mountain Lion. I called the Apple guy at the Apple care support but without any luck.
    At the end--at least in my case, but it could also be yours--I think I have understood what was going on. This happens when you have your Apple ID registered on more than one device. In my case, we have two iPhones--one for me and one for my wife--but with the same App Store account. So, when I sent an sms via iMessage for the Mac, the receiver was shown my wife's iPhone number.
    I hope I have been clear enough, you know, explaining this in a foreing language is always painful...
    Ciao,
    Antonio
    P.S.: this could be true for similar issues (iMessage wrong sender) that I've read in the Mountain Lion, iPad and iPod forums.

  • Receive error when starting iTunes

    Receive error when starting iTunes "The registry settings used by the iTunes drivers for importing and burning CDs and DVDs are missing. This can happen as a result of installing other CD burning software. Please reinstall iTunes" I have with no success.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    iTunes for Windows: "Registry settings" warning when opening iTunes

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

Maybe you are looking for

  • How can I do a Hard Reset on my apple tv 2nd gen, Thanks Guys

    I messed with my AppleTv, DMS configurations in order to try and get it updated.  Now it wont connect to my internet.  Is there any way to do a hard reset on the device to restore it to factory settings?  Thanks guys

  • Print Booklet - OS X - PS to PDF with Preview, and a mysterious line?

    Hi, I'm preparing something for print, and I've run into a couple of questions I'd love some advice on. The printshop wants the A5 booklet as a A4+bleed PDF, so I'm producing 'Print Booklet' to a Postscript with the PDF PPD and using Apple's Preview

  • User not listed  in sudoers file OSX Mavericks

    When attempting to backup the hosts file (or any other command in Terminal), this message appears after entering the password. "[username] is not in the sudoers file.  This incident will be reported." The username is in fact listed as an admin accoun

  • Duplicating or moving resources

    I sure am getting a lot of crashes if I try to drag and drop resources (a skin or something) from one folder to another in the tree. Also, I've always duplicated files in the tree with control-c and control-v and it makes a Copy of the file. Apparent

  • Can I Burn CD from Radio Station's Streaming Audio?

    does iTunes allow me to record audio streaming from a radio station's website? if so, how do i do it? thanx.