Permission errors may occur under the following conditions:
When the script was created you were logged in as user X. At the time of backup you are logged in as user Y who does not have permission to connect to the source server: -1001 (unknown Windows error)
When the script was created you were logged in as user X. At the time of backup you are not logged in: -1017 (insufficient permissions)
You may need to configure the Retrospect Launcher Service to automatically log into the shared volume using a non-"system" account for proper login to the shared network volume as follows:
Open the Services Control Panel under Administrative Tools.
Select Retrospect Launcher, stop the service and then click the Startup button.
In the "Log On As" section select This Account. LocalSystem will appear in the field to the right.
Change "LocalSystem" to the account you want to use and then enter your password in the two password fields.
Restart the Launcher Service.
Retrospect 6.5 and later includes an option to configure Retrospect to run under a specific user account. This should allow a backup of a mapped volume without needing to modify the launcher service.
Go to Configure>Preferences>Security. Configure Retrospect to run as a specific user.
Note: Users in a Domain should enter the domain name in the "log on to" field of the security preferences. If you are in a workgroup environment, enter the local computer name into the "log on to" field.
You should also go to Configure>Volumes. Get properties on the network volume and configure it for automatic login.
Last Update: 14 February, 2012