Robo-FTP Server

Frequently Asked Questions

The FAQ list is a great starting point for basic questions about what you can do with Robo-FTP.

Orange_arrowOrange_arrow Browse the FAQ list now

Getting Started

Browse these tutorials and sample scripts to get up and running with Robo-FTP in minutes.

Orange_arrowOrange_arrow Browse tutorials and samples now

Contact Technical Support

If you can't find the answers you need online, get in touch with our Technical Support staff.

Orange_arrowOrange_arrow Contact Technical Support now

Professional Services

Need more than basic technical support? Our Professional Services team can help you deploy a complete solution.

Orange_arrowOrange_arrow Contact Professional Services now

Enter search queries below or use the tag links to the right to browse the knowledge base by category (Show All Tags).

Use the PATH environment variable instead of the full path to Robo-FTP.exe

The supported method of running Robo-FTP from the command line (batch file, ASP script, scheduler, EXEC command etc.) is to add the installation directory to the PATH environment variable rather than hard-coding the path for Robo-FTP.exe.

When Robo-FTP is installed in this manner the migration process for new major releases is easier and safer because you can test all of your command scripts in "side-by-side" mode without disabling processes currently running on your existing version of Robo-FTP.

When are are ready to begin using the new version system-wide, simply update the PATH environment variable and existing calls to Robo-FTP.exe will launch the new version.

Note: Environment variables are user-specific so don't forget to update the PATH for any service accounts used to execute Robo-FTP command scripts.

Article last updated: 2017-01-23

Tags: Robo-FTP, PATH, environment variable

Home | Solutions | Professional Services | Technical Support | Download | Company | Contact Us | Partners | Site Map | Terms of Service | Privacy Policy | Buy Now