Jump to content

smithpd

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About smithpd

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  1. smithpd

    Retrospect 7.7 Windows, error -1017

    Thanks for your help. I understand about the C drive. That is why I removed the share soon after i made it. It just happened by coincidence to make Retrospect work. In fact, I did install the OS by a slightly dubious method. I won't go into detail, because I think it does not matter. The end result is that the OS and Retrospect seem to be working.
  2. smithpd

    Retrospect 7.7 Windows, error -1017

    By rebuilt hard drive, I mean that it is a fresh install of Windows on a drive that previously did not have Windows installed. I am using Windows XP Pro 32 bit. I don't understand how I could not have the permissions. I am an administrator with full control on both the server and the client computers. Why would not matter with the client setup? Can't the client computer operator change permissions and still have the backup work? Anyway, I think I know what may have caused the problem, but I do not know why. Just before running the script I made a share of the C drive on the client computer, giving me full access. With the share active, I got the 1017 errors. Then I removed the share and ran the backup again. This time I did not get the 1017 error, but I got a bunch of 1011 errors when comparing after the snapshot. Not liking that, I changed the script to output to a new Backup Set and ran the script again. This time, it ran without errors. So, it is working now, but I don't know why, and I don't know why it failed before. Can you shed any light on this?
  3. I am using Windows Retrospect Professionsl 7.7.620 (32 bit). I am running a backup script on a client's C: drive. I get the following error immediately on starting the script: Can't use Open File Backup option for Local Disk (C:) on xxxx_pc, error -1017 ( insufficient permissions) Then it proceeds to run and verify the complete backup with a few (6) other errors, mainly about different modify dates changing on files such as log files. What exactly does this error mean, and how can I fix it? I never saw this before. This is a fresh install of Retrospect on a rebuilt hard drive. It previously ran without errors. Windows Firewall has Retrospect and Retrospect client properly excluded on both sides.
  4. smithpd

    error -1001 (unknown Windows OS error)

    Somehow I am not quite convinced by that argument, Andrew. As I said earlier, I can restore from the backup set just fine, so the catalog is not corrupt as it stands. I can copy many large files over the LAN without problems. My LAN is reliable. Retrospect is the only problem. It seems to me that Retrospect is being fussy. My theory is that the fussiness is Retrospect 5.5's inability to cope with real life, probably a communications bug. If packets are being lost, why does Retrospect have a problem with it but Windows does not?
  5. smithpd

    error -1001 (unknown Windows OS error)

    Thanks, AndrewA. That seems like sound advice. I was considering that, but this is one last-ditch effort to see if I can make 5.5 work. Certainly a free trial would be a way to go. The funny thing is that 5.5 has worked fine for me in this same general configuration. This error depends on something that I do not understand, such as the phase of the moon. By the way, why would I want to keep the catalog locally and the backup set remotely, other than to circumvent a bug? The idea (to me) is to keep the backup independent of the computer that might crash.
  6. I am using Retrospect 5.5 for Windows. I have a frequent problem with the following type of error message when I try to add incrementally to an existing backup set, which is located on a Windows network share (not mapped to a drive letter): + Executing Immediate Backup at 7/19/2010 4:30 PM MapError: unknown Windows error 1,224 TFile::SetEOF: SetEndOfFile failed, \\Betty-pc\Peter Backup\Backup Set E.rbf, winerr 1224, error -1001 Can't access backup set Backup Set E, error -1001 (unknown Windows OS error) 7/19/2010 4:30:36 PM: Execution incomplete Quit at 7/19/2010 4:31 PM I am running Retrospect on my machine, pushing the data from my machine to a backup set located on a share on my wife's machine. Both computers involved are running Windows XP Pro SP3. I can create a new backup set on the same share. I can restore files from the same backup set (Backup Set E) that I am attempting to add to. I can forget about and re-open the backup set. I can write files to the folder, and I can edit and change those files using other software, e.g., Notepad. When I attempt to use Immediate Backup to add incrementally to the existing backup set, Retrospect opens a separate file for the catalog, I think, entitled ???.rbc.rbc. It writes a little to it, then it hangs. I have done the following with no success: Turned off Windows Firewall Entered Retrospect 5.5 as programs that are allowed by the firewall on both sides. Reinstalled the Retrospect 5.5 software. Changed permissions on the directory in which the backup set is located so everyone has full access to the files. I am running as a person with Admin privileges. I am using a Linksys router to connect several computers in my office. I am not aware of any connectivity problems with the router. Any ideas how to fix this?
×