BizTalk receiving flat file from SFTP location,getting pipeline error,but once file save in tracking instance,saving partial file.
SFTP configured in SFTP v2. and In SFTP location correct file is there.why full file not received in biztalk.file flat around 10 MB size.

This issue is due to your SFTP server not with your client BizTalk or its SFTP adapter. Some SFTP or FTP servers do have a feature called file lock until its being written. Once the file has been completely written into the SFTP folder, the process from server should release the lock for clients (like BizTalk adapter) to pick the files. This feature must be applied (or should be considered mandatory) when dealing with large files as in your case 10MB file. In some cases of SFTP server, dont apply locks while files being written to SFTP folder and this causes the clients/processes which access the files from SFTP folder to process the partial files.

Some SFTPs who doesnt have file lock feature follow various methods to avoid, other processes/clients to access the files while files being written. Features  like renaming a file to a different extension while its being written (like xxxx.txt.temp) and once the files have been completely written off, they change the file to actual extension back to original one (xxxx.txt)

I would not completely put the blame to SFTP server. SFTP adapter in BizTalk also can share the blame. The out-of-box adapter as of now doesnt have any feature (properties) to execute a command as we can do with FTP adapter or with other SFTP adapter (like nSoftware SFTP adapter or bLogical SFTP adapter). If you have feature like execute a FTP-style commands like Before GET or temporary remote directory you can (client can) either rename the file (using  Before Get and move the renamed file) or using temporary remote directory  feature you can move the files to a temp folder before copying the file to destination.

But as of now out-of-box adapter doesnt have these feature, hopefully they may come in future versions/release. So to find solution for your problem now, speak with your SFTP server and ask them to make file available to others processes/clients once its been completely written.

Regards,

M.R.Ashwin Prabhu

You need to post the exact error message.

It sounds like the SFTP server is cutting the connection, or maybe the network.  The Adapter may not know this and any Pipeline code certainly wouldn't.

As M.R.Ashwin Prabhu correctly states, this is server problem (them) not a client problem (BizTalk, you).

In SFTP server already files will present, from through recieve location service window will recieve the file
example our receive location service window is 2:00 to 4:00.
and file is present in SFTP location with 1:00 creation time.
I dont think here file lock,written problem will be there as u mentioned.we are using nsoftware v3 SFTP

once 2:00 clock BizTalk receive reads file from SFTP,then fail in pipeline, because file is not validated in pipeline, and document schema,recieved file partial so.. I hope my problem understood

You need to post the exact error text.

Copy it from the Event Log.

If youre using nSoftwares SFTP adapter, they number of Tuning properties available for SFTP adapter.

• Max Batch Size
• Max File Size

Also if its due to server issues as we explained, you can mitigate it using nSoftware properties like

• Before Get
• Temp Path

Following is the SFT properties documentation from nSoftware.

http://www.nsoftware.com/kb/articles/biztalksftpadapter.rst#receiveport

Also most of their adapters have logging function which could help you in this case.

Most importantly, you can contact nSoftware support to deal with this issue. So contact them.

Regards,

M.R.Ashwin Prabhu

Event Viewer Pipeline failure error.

because file is not validated in pipeline, and document schema,recieved file partial so..

If I save file from Admin console and validate in schema, same error because.. of partial half file.

so same in pipline error.

Event Viewer Pipeline failure error.

Sorry if I'm not being clear but you need to post the exact entire error from the Event Viewer.

You can also try with a PassThrough Pipeline to see how much of the file you receive and where/if it's cut off.