Enter search queries below or use the tag links to the right to browse the knowledge base by category (Show All Tags).
Existing script can't access a network resource when run on a new computer
Windows account permissions are usually to blame if your Robo-FTP command script is not able to access a network share when run from another machine.
Log in to the new computer and verify that you are actually able to browse to the desired network share using the Windows Explorer. If you are able to access the share via its Universal Naming Convention (UNC) name it is likely that Robo-FTP is being launched by an account with insufficient permissions to access that share or that the script uses a mapped drive that is not defined on the new computer.
If Robo-FTP is running as a Windows Service, it may be running under the Local System account which does not have permission to access network resources. Examine the Help file for information about using the Service Installer to change the account to one that has (or may be granted) the required access permissions.
Note: Microsoft recommends using a UNC path instead of a mapped drive to access network files from a service. See: http://msdn.microsoft.com/en-us/library/windows/desktop/ms685143(v=vs.85).aspx
If Robo-FTP is being launched by a Scheduled Task you can modify the account by editing the task security properties in the Windows Task Scheduler.
See also:
File/folder open error after moving to a new computer or new version of Robo-FTP
Nothing happens when running Robo-FTP as a service
DOSCMD and mapping a network drive
Article last updated: 2022-01-07
Tags: UNC, network, share, permission, permissions, access, new computer, new machine, account, login