Frequently Asked Questions
The FAQ list is a great starting point for basic questions about what you can do with Robo-FTP.
Browse the FAQ list now
Browse these tutorials and sample scripts to get up and running with Robo-FTP in minutes.
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.
Contact Technical Support now
Need more than basic technical support? Our Professional Services team can help you deploy a complete solution.
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).
My script does not work as a service, and/or does not create a log file.
This problem can happen when script operations rely on permission to access a local folder or a network share.
File and folder access problems usually cause errors that are reported in the Script Log (although certain problems are always written to the Trace Log.) These problems can be difficult to troubleshoot when Robo-FTP also lacks the necessary permission to create or update the log files.
This problem can usually be resolved by using the Service Installer program to change which Windows Account is used to launch Robo-FTP.
Nothing happens when running Robo-FTP as a service
Script failure, when running Robo-FTP as a service, when it attempts to access a network share.
DOSCMD and mapping a network drive
Article last updated: 2012-06-20
Tags: Robo-FTP, Services, Network Share