Jump to content

JEtkins

Members
  • Content count

    50
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JEtkins

  • Rank
    Occasional Forum Poster
  1. JEtkins

    Version 7.7 - Writer "ASR Writer" backup failed

    The backup sets were created under 7.6, but I have reset them, removed all the members, and created new ones on my NAS under 7.7 I may be wrong, but I think I'm only seeing these errors the first time a backup runs after a reboot. I reboot rarely, so I can't readily verify that observation, but I'll make a point of watching for it next time I do.
  2. JEtkins

    7.7 does not fix failure to launch on schedule

    I too have been having problems with scheduled executions not launching under 64-bit Vista or Win7. I had Retrospect set to run as the specified user, because I back up to password-protected NAS storage. I had tried also setting the Retrospect Launcher task to run under the same account, but to no avail. Finally, thanks to the suggestions in this thread, I have it working by running the Launcher service under the desired user account, and setting Retrospect to run as the logged-in user. Scheduled backups now run on schedule, and for the first time ever, I can actualy see a progress bar in the Retrospect Monitor window if I try to open Retrospect while one is running. I'm running Retrospect Pro 7.7 plus the latest RDU, under 64-bit Win7 Ultimate.
  3. JEtkins

    Version 7.7 - Writer "ASR Writer" backup failed

    I'm seeing similar errors, but not on every run. Here's two otherwise-identical backup runs from within the same instance of Retrospect (i.e without closing the app between backups, so whatever permissions it had for the first run it also had for the second, and vice versa: Retrospect 7.7 Pro (with latest RDU), running as Administrator under 64-bit Win7 Ultimate
  4. JEtkins

    Retrospect Launcher not launching on Win7

    Is there an ETA? Win7 has been RTM for over a month now, and is available to everyone except Joe Consumer. I trust this will not require us to purchase an upgrade?
  5. I recently upgraded my workstation from Vista Ultimate x64 to Windows 7 Ultimate x64 RTM. I run Retrospect Professional on this machine, backing up to two rotating backup sets on my NAS. Since the upgrade, the automated backups are no longer firing off at their scheduled times. If I manually start Retrospect, the scheduled executions start running immediately. The launcher service is running under the local system account, and appears to be running fine; it's just not firing off the scheduled backups. (They do run on schedule if I leave Retrospect open.) Perhaps this is related to another oddity I noticed today: despite my Preferences being set to run Retrospect under a specific user account, that no longer appears to be happening. Where previously the log would show it now shows simply Any suggestions welcomed.
  6. JEtkins

    Vista , 7.6 and Activity Monitor

    I ran Process Explorer with "Show processes from all users" selected, but there was no sign of any retro process at all, despite the gray box's insistence that it was waiting on one to finish. The weird thing was that there were no backups scheduled or running, and I had just closed Retrospect not ten seconds earlier - I was trying to open it again because I had forgotten to check something before closing it.
  7. JEtkins

    Vista , 7.6 and Activity Monitor

    I'm yet another voice in the wilderness with same problem, it seems. After taking the advice to rename retromonitor.exe to .old, I now have a gray box telling me it's waiting for another instance to exit, despite the fact that there is no other instance of retrospect, retromonitor, retrorun, or retro-anyotherdamnedthing running. *sigh* Looks like yet another reboot. This has been going on for, what, almost a year now? And it's going to be fixed in 8.0, for which we're going to have to pay an upgrade fee? Great.
  8. JEtkins

    Another 1017 error

    Any other ideas, or clues when this might be resolved? I'm still seeing -1017 failures on the first automated run after a reboot.
  9. JEtkins

    Another 1017 error

    OK, I set it to run as the logged-in user, but got exactly the same 1017 error when trying to save the Snapshot file. The catalogs folder - and the catalog files themselves - have Full Control permissions for both my user account and SYSTEM.
  10. JEtkins

    Another 1017 error

    OK, I need to eat some humble pie - it failed appears that the failure was due to it being unable to groom sufficient free space out of the backup set, not because it could not access the set. I do have a stored ID/password for the network share, so perhaps it will be able to access it regardless. I'll try again over the weekend. It would have been nice to be able to see what was going on at the time if the Retrospect Monitor window was working properly, though.
  11. JEtkins

    Another 1017 error

    Well that went well...not! As I suspected, the auto-launched task is not able to access the backup set on the network share, so I've now got a background process running, emailing me that it's waiting for media, and no way to connect to it to stop it. When I try to open Retrospect, I instead get a blank Retrospect Monitor window (another problem which is the subject of another thread already), so it appears that my only option is to attempt to kill the running process, or reboot. Past experience tells me that either of those actions will result in a corrupted catalog file, so I'll then have to manually recreate that as well. Much as I like Retrospect, I'm beginning to have some serious doubts about its readiness for Vista, which is very disappointing considering how long both products have been around now.
  12. JEtkins

    Another 1017 error

    I'll give it a try, but won't that create problems accessing the network share that I'm backing up to?
  13. JEtkins

    Another 1017 error

    OK, apparently I'm not using the right words. No, it is not set to "currently logged-in user" - the account is set manually.
  14. JEtkins

    Another 1017 error

    Sorry, I thought I mentioned that in my original post. It's set to run explicitly under my account.
  15. JEtkins

    Another 1017 error

    The catalog in on my local C: drive, in that account's Documents folder. FYI, I have two identically-configured backup sets, with the script alternating between them on a weekly basis, and the error occurs regardless of which is the current set.
×