Jump to content

haggis999

Members
  • Content count

    108
  • Joined

  • Last visited

Community Reputation

2 Neutral

About haggis999

  • Rank
    Occasional Forum Poster
  1. Catalog Files on a NAS

    Thanks for persevering with this, David. I will do as you suggest and check out that KB article more carefully over the coming weekend.
  2. Error -1017 (insufficient permissions)

    Thanks for that link. I've now posted a question on that other thread.
  3. Catalog Files on a NAS

    I've just checked the member properties as Scillonian advised and found that the location is already in UNC format (\\PRIMARYNAS\Backup\). However, the job in question actually saves the backup in \\PRIMARYNAS\Backup\My Pictures. You suggest that this might be a problem, but the job has been running successfully for many years. It's only become an issue since Windows 10 decided to forget my NAS boxes. I already have my primary NAS listed under Quick access. That's useful in Windows Explorer, but doesn't help Retrospect find the NAS when running an automated job using the Retrospect Launcher.
  4. Catalog Files on a NAS

    I'm hitting similar problems with Windows 10 occasionally losing the ability to discover the NAS boxes on my home network, a situation that is currently preventing one of my automated backup jobs from running (though it works fine if I open Retrospect manually before the job is due to start). Rather oddly, several other automated backup jobs that use the same NAS (though not the same destination folder) continue to run fine. I've just upgraded to V12.5, but it made no difference. However, I have not yet found a way in Retrospect to specify the backup destination using the UNC path. I would appreciate some guidance on this point.
  5. Error -1017 (insufficient permissions)

    That KB article doesn't appear to contain anything relevant. It merely addresses some of the basic issues regarding how to configure Retrospect for auto launching, something I sorted out a long time ago. However, it now appears that an issue with the Windows 10 network discovery process is the most likely source of my problem. If I open up Windows Explorer and click on the Network icon, it is not currently displaying my NAS drives (something it normally does), though they are listed under 'Other devices'. I have seen this before and have never found the cause, but it just tends to go away after a few days and everything returns to normal. It's very irritating. Grrrrrrr.
  6. Error -1017 (insufficient permissions)

    Having found nothing relevant so far in previous posts about error -1107, I decided to pay for the upgrade to V12.5. Sadly, it made no difference. I still get the same error.
  7. Error -1017 (insufficient permissions)

    Hi David, The KB article just appears to address initial setup issues for automated backups. I did that successfully a long time ago. Thanks for the search advice. I had already run a search for Error -1017 in the Professional forum, but this produced a long list of hits relating to different error messages, despite the results being sorted by relevancy. A search for "-1017" was much more useful, though I fail to see why my original search did not include these results. I will now check out those previous posts to see if I can find anything of use in my current situation.
  8. I'm running Retrospect Professional 10.5 under Windows 10 and my backups are stored on a Synology NAS. I have several automated daily backup jobs that have been running successfully for several years, but one of them has recently started to fail with the following error message. Can't access volume XXXX on YYYY, error -1017 (insufficient permissions) My Startup Preferences are configured to use the Retrospect Launcher service, so Retrospect is normally opened and closed automatically. If I open Retrospect manually and leave it open then the job works fine, but when Retrospect is left to launch automatically then it always fails. I have not altered anything in my Retrospect configuration for a very long time and can't think of any reason why its behaviour should have changed during the past few days. Any suggestions would be gratefully received.
  9. Scheduled jobs failed but no alerts were generated!

    Hi JoTRaGo, You have correctly identified the source of my problem! Your post immediately reminded me that I had recently disabled a bunch of services via msconfig.exe as part of an attempt to diagnose some other problem. This happened at around the time my backups began to fail. A quick check showed that the Retrospect launcher is still disabled. Many thanks for your help. Senior moments like this happen when you get older David
  10. Scheduled jobs failed but no alerts were generated!

    Hi Lennart, My startup preferences are the same as yours, with the one exception that I have chosen to exit after the completion of each job. That does not look like an important difference. I have received several problem alerts in the past when there was an issue with the availability of the NAS box that is the target of my backups. This is the first time I have become aware of a problem that did not generate an alert. David
  11. I am running Retrospect Professional 9.5 under 64-bit Windows 7 and have just become aware that none of my scheduled backup jobs have been running for the past 3 weeks! It was very careless of me to miss this problem for so long, especially as I have email alerts set up to notify me when each backup has completed. My only excuse is that I have been extremely busy and the absence of the Retrospect confirmation emails among other similar emails I get from my Synology NAS boxes just didn't catch my attention. At the age of 71 you also get a bit forgetful... Another reason for my failure to notice this problem is that I thought I would receive automatic alerts from Retrospect if there was any problem that prevented my scheduled backup jobs from running. No such alerts were ever received. A minute or so after I manually started Retrospect this morning, all of these long-delayed jobs automatically started to run one after the other. I did nothing to prompt this. I had previously selected the 'Notify for failures and media' checkbox under Preferences => Notification => Alerts. Can anyone offer a possible explanation for why that has not worked in this case? David
  12. No room for snapshot?

    I will try to fix that problem by moving some applications from my C: drive to one of my bigger drives. David
  13. No room for snapshot?

    Lennart, Uninstalling Adobe CS4 resulted in the free space on my C: drive increasing to over 9GB. That appears to have fixed my problem, as the relevant Retrospect backup job ran without error this afternoon. Thanks for your help on this . David
  14. No room for snapshot?

    Thanks for that useful information, Lennart. I've just realised that I still have the Adobe CS4 Suite installed on the C: drive (I'm currently using CS6, which is installed on my G: drive). Uninstalling CS4 should therefore release a fair bit of free space. David
  15. No room for snapshot?

    My C: drive is a 160GB SSD, so does not have plenty of spare storage space. I also have two 1TB drives installed on my PC. Is there no way to tell Retrospect to use a different location for its Temp folder? However, is this relevant to my original problem? David
×