File Transfer Server could not be started or it exited unexpectedly. Exit value 0 was returned

One of our researcher was trying to sftp from his Windows Box to a Linux Server and he encounter this error "File Transfer Server could not be started or it exited unexpectedly. Exit value 0 was returned"

When someone launched a sFTP session, the user start-up scripts such as .bashrc and .bash_profile is evoked. Often the root cause of the error is erronous statement in the .bashrc or .bash_profile.

1. Often, the users evoked a csh or tcsh while on the default interpreter is bash.
2. Sometimes it is also due to erronous message which are meant for interative logon like output text messages etc.

With a bit of correction, your sftp will works.

See similar problems like

1. Resolution for bash orted command not found
2. Unable to source path during non-interactive ssh session  
3. bash: scp: command not found

For other notes, see

1. SSH FAQ on sftp corruption