Jump to content
Sign in to follow this  
barnard

1017 Errors

Recommended Posts

I am having the same problem described by others, using Retrospect 6 under XP Pro. Scripts that backup Novell netware drives simply do not complete when Retrospect is not running. I am the only one using this computer. I always login under the same name. All network drives are visible. I have followed all the instructions about stopping and starting the service, entering my login name and pw, etc, rebooting.... Everything suggested, but the script will only run when Retrospect is already running. Otherwise, I get this message:

 

 

 

"Can't access volume MAIL on Staff on Athena, error -1017 (insufficient permissions)"

 

 

 

Scripts that simply backup local drives seem to run fine.

 

 

 

Please do not simply reprint the material from the knowledge base about the RetroLauncher service. It seems to be configured properly to run automatically under my XP User Name and pw. (The account appears as ".\MyFName MyLName")

 

 

 

What can be done to fix this?

Share this post


Link to post
Share on other sites

Go to Configure > Volumes. Right click on the network volume and get properties. Click on the network icon in the top left corner and enter the appropriate user name/password combination.

Share this post


Link to post
Share on other sites

Setting the pw in the Configure...volume properties worked once, but then when I replayed the script 5 minutes later, it failed with another 1017 error. (In addition, I get screen redraw errors and the program fails to close properly, but that's another subject!) This is very frustrating.

Share this post


Link to post
Share on other sites

When Retrospect autolaunches, the program uses the permissions allowed by Windows for the user name/password combination specified in the launcher service. If the user name/password combination you are using still do not allow proper access to the share, you may need to check the allowed permissions.

 

 

 

In reply to:

I get screen redraw errors


This is a known issue in some configurations when changing the launcher service in WinXP. We are actively investigating this issue.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×