Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Failed to set default directory / file specification syntax error

Please attach a full session log file showing the problem (using the latest version of WinSCP).

Though note that WinSCP does not support well servers, that do not follow common *nix path format (like IBM VMS, MVS, etc).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
jrifkind1

Failed to set default directory / file specification syntax error

We work with a company who requires that data files be transferred via FTP, and we have historically used to Filezilla to accomplish this. We're wanting to transition to using WinSCP in order to automate the upload process, but when I attempt connect to our partner's FTP site (using the same credentials that were used to successully connect with Filezilla), I receive the an error saying:

"Could not retrieve directory listing
Failed to set default directory to /DKC2:[CLIENTS.TQL]
file specification syntax error"

It appears that I'm able to connect to their FTP site, yet am unable to connect to the correct remote directory. Again, I'm using the same credentials that I've been using to upload files through Filezilla. Does this look like an issue with the way the client is configured? Any help would be greatly appreciated.

Thanks!

Documentation

Support

Associations

Follow Us