Enter search queries below or use the tag links to the right to browse the knowledge base by category (Show All Tags).
Script failure, when running Robo-FTP as a service, when it attempts to access a network share.
Beginning with v1.50.0, you might try installing the Robo-FTP service to run under a user account that has access to a particular network share.
Prior to v1.50.0, the issue is that when Robo-FTP is running "normally", a user has logged onto Windows and the user must have access privileges to the network share. When Robo-FTP is running as a service, there is no user logged on and this network share has not been mounted. This can be resolved by having the Robo-FTP script mount the network drive before attempting to access it.
In either case, you might try using the EXEC script command to run the Windows 'net' command. For example, to mount a network drive, say drive G, issue a command such as:
EXEC "net use G: \\server\path"
Do this before attempting to access drive G.
If you need to submit a user name and password to connect to the network share, the command might look something like this:
EXEC "net use G: \\server\path mypassword /user:mydomain\myusername"
For more details about the net use command, here is an article from Microsoft's knowledge base:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/net_use.mspx?mfr=true
Tags: Robo-FTP, Services, Network Share