Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Incoming FTP file is LOST in PipeLine
- This topic has 4 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
January 6, 2010 at 4:45 PM #24012
Hi:
We are on Visual Studio 2005 Professional, BizTalk Server 2006 R2 Enterprise. We are using nSoftware to pick a file from a remote SFTP server. We have defined a Receive SFTP PipePline for this. Our receive port on our orchestration is using this receive pipeline. Once we get the file, we expect the file to go into message box and then to its final destination which is specified in the send port of our orchestration. But this won’t happen. File is lost. Can we capure this file somewhere as soon we get it and before the message box starts processing it ?
-
January 6, 2010 at 6:31 PM #24013
To get a better understanding of what is happening, you can use BizTalk’s tracking capabilities. To start with you can enable tracking on the receive port to see what the stream looks like as the port receives it and then see if it gets to the message box.
-
January 7, 2010 at 12:36 PM #24018
Thanks Walter:
Actually the xml file does come into our Archive folder which we have specfied in the configuration pipeline properties of the receive pipleline. But the event log gives below error.
A message received by adapter “nsoftware.SFTP v3” on receive location “RcvEmployeeBatch_SFTP” with URI “SFTP://[email protected]:22233/*.xml” is suspended.
Error details: There was a failure executing the receive pipeline: “XYZ.PROJ.Pipelines.ReceiveXYZBatchPipeline, XVZ.PROJ.Pipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c1234334333434” Source: “PSTBatchStamp” Receive Port: “RcvEmployeeBatch” URI: “SFTP://://[email protected]:22233/*.xml” Reason: Root element is missing.
MessageId: {01121212121212121212232323232332323}
InstanceID: 123455666-323232323-2323-3439-34343434}
For more information, see Help and Support Center at
-
January 7, 2010 at 5:02 PM #24021
If the input message is XML make sure that it validates against the expected schema. The error suggests that the root element is not what is expected (possibly wrong namespace).
-
January 7, 2010 at 6:00 PM #24022
The “root element is missing” error means the Xml Disassembler or endpoint manager cannot find the message.
It is possible that the stream you returned from your custom archive component has not been reset to the start position.
Does your custom component read the stream and write the file before returning? If so you need to reset the stream position to zero.
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.