Jump to content

haggis999

Members
  • Content count

    160
  • Joined

  • Last visited

Community Reputation

2 Neutral

About haggis999

  • Rank
    Occasional Forum Poster

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. haggis999

    Retrospect Launcher service not working

    I suspect that this may be the cause of a new error I hit after attempting to dispense with using the Retrospect Launcher Service. After launching a non-UAC prompting version of Retrospect via the Windows Start-up folder, as previously described, and turning off the Launcher Service, I found that the Retrospect duplication script that is triggered first every day could not gain access to any network resources. Even when I tried to manually update the destination, I got -1016 errors. The Knowledgebase article that covers the similar -1017 error is over 6 years old and did not provide any useful assistance. However, I'm struggling to think of why any user other than my own normal Windows account is involved in this scenario. In the meantime, I have turned the Launcher Service back on and that duplication script ran OK this morning.
  2. haggis999

    Retrospect Launcher service not working

    My understanding is that the Launcher Service will use the SYSTEM login, so I was really expecting Job #2 to fail with an error -1017 (insufficient permissions) as its destination folder on the NAS allows no access for the SYSTEM account. I was therefore rather surprised to be presented with a login prompt for Job #2. When this happened, I entered my normal login details, which were accepted. However, this is now purely of academic interest. Thanks to your assistance, my problem is now fixed.
  3. haggis999

    Retrospect Launcher service not working

    Interestingly, my second scheduled job to run under an automatically-launched version of Retrospect generated a popup to request login credentials for my NAS. The first job, which has never recently generated such a popup, was a duplication, while the second job was a backup. I have no idea why they behaved differently. As a test, I scheduled another run of the same backup job and this time it remembered the previously entered credentials, so all appeared to be well. However, I then realised that there was no longer any need to use the Retrospect Launcher Service, as I am now successfully starting Retrospect automatically via Windows. Turning off the launcher meant that my scheduled scripts are now being run under my normal login, so I was able to delete the NAS folder access permission I had just given to the SYSTEM user.
  4. haggis999

    Retrospect Launcher service not working

    The Retrospect Launcher service is indeed set to Automatic. It was working, but failed to fully open Retrospect because of the UAC prompt issue highlighted by Scillonian. I went looking for a way to bypass the UAC prompt for a specific program. The following Youtube clip tells you how you can create a special shortcut for this purpose using the Windows Scheduler. I then added that new shortcut to my Windows Start-up folder instead of a direct shortcut to Retrospect.exe. https://www.youtube.com/watch?v=Ai_l_L-8o-c This successfully opens Retrospect every time I start Windows, so I no longer have to start it manually every morning. I thought my problems would now be over, but my first scheduled task still failed with the same permissions error. Given that I never got this error when opening Retrospect manually, there had to be something different happening when using the Launcher Service. It then occurred to me that perhaps my NAS does not see the access request as coming from my normal login. Up to now, only 'adminstrators' had any access to the destination folder on the NAS. Adding a permission for 'SYSTEM' to have read/write access made my Retrospect problem disappear! Many thanks to Scillonian, who set me on the right track to resolving this long-standing problem
  5. haggis999

    Retrospect Launcher service not working

    I'm in full zombie mode when I respond to those regular UAC prompts, so that never occurred to me. That fully explains the problem. Many thanks for shedding light on the matter Thanks also for the info about AutoIt. I will check that out.
  6. haggis999

    Retrospect Launcher service not working

    BTW, there is more than one Startup folder in Windows 10. The folder where I put a shortcut to Retrospect.exe is shown below. Just as a test, I added a Photoshop shortcut to this same folder and restarted my PC. As soon as I logged into my Windows user account, a Photoshop window appeared on my desktop. Does anyone know why Retrospect does not start up automatically in a similar manner? C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Start-up
  7. haggis999

    Retrospect Launcher service not working

    I have just unearthed some advice I got from Retrospect tech support back in 2013. They told me that the Retrospect preference setting 'Always run Retrospect as the specified user' would not work unless you disabled Microsoft's User Access Control (UAC), which would generate a security risk. That would explain why my test of that setting the other day just ignored my scheduled jobs. I have now returned to using the 'Run Retrospect as the logged in user' setting. Needless to say, my first scheduled job of the day once again fails with the -1017 (insufficient permissions) error. The job in question duplicates the folder G:\My Pictures from the PC that is running Retrospect to a folder on my Synology NAS. The security settings for G:\My Pictures show my normal Windows user account as the owner of the folder, so that looks OK. The login credentials for my NAS were saved by Windows a long time ago, though I don't know where. Accessing the relevant NAS folder via Windows File Manager works fine without any need to repeat a manual login process. Back in 2013, Retrospect tech support advised me to "manually open Retrospect and leaving it running prior to a scheduled backup operation. This will give you full access to the user interface so that you can view what Retrospect is doing and troubleshoot any issues that may come up during a backup, such as a media request dialog box". That is indeed the only method that works at present. However, if I could find a way to make Windows 10 automatically start up the full Retrospect app at boot time, that should achieve the same objective with less hassle. Unfortunately, putting a shortcut to Retrospect.exe in my Startup folder doesn't actually work as I expected. It just seems to start some Retrospect-related processes rather than the full application.
  8. haggis999

    Retrospect Launcher service not working

    No, I didn't realise that was necessary. However, I have now restarted the computer and set up a one-off backup job to run in a couple of minutes. While watching Task Manager, I could see the Retrospect process starting at the specified time, but after waiting for longer than this job was expected to take, I had still received no automated email message to confirm its status. I then launched Retrospect manually, which had the effect of triggering the start of the one-off job I had created. In other words, the only automated action had been to start the Retrospect process. My scheduled job had been ignored. We seem to be making a degree of progress, but the final goal has not yet been achieved
  9. haggis999

    Retrospect Launcher service not working

    I removed retrospect.exe from my Start-Up folder and then changed my Retrospect preferences to select "Always run Retrospect as the specified user", using my normal Windows login credentials. I also stopped the Retrospect process that was currently listed on Task Manager (as a result of my previous Start-Up setting). Unfortunately, it has not fixed the problem. My next automated backup script was due to start 10 mins ago, but nothing happened. The fact that this overdue backup commenced as soon as I started Retrospect manually proves that the Launcher service never worked. I don't think it even tried to work, as no error message has been logged.
  10. haggis999

    Retrospect Launcher service not working

    My preferences are also set to 'Run Retrospect as the logged-in user'. I don't think I had a shortcut in the Startup folder back when the Launcher service used to work. It was only added as a result of a suggestion from David Hertzberg, one of the resident gurus on this forum, though I'm struggling to find the thread where that got mentioned (I think it was in April 2018). I first raised this topic via the following thread in October 2017, http://forums.retrospect.com/topic/154427-error-1017-insufficient-permissions/, but it never generated a solution. On re-reading that old thread, I see that the problem actually first arose under Windows 10. It always worked under Windows 7.
  11. If I remember correctly, I was still using Windows 7 when the autolaunch facility of Retrospect stopped working. It was certainly quite a long time ago. I'm now on Windows 10, and running a later version of Retrospect, but nothing has changed. To get around the problem, I have been manually starting Retrospect 12.6.1 every morning. When I mentioned this in a thread on another topic earlier this year, I was advised to leave Retrospect running all the time I am using my PC. It's possible that such a shortcut was always there, but I can now confirm that my Startup folder contains a shortcut to Retrospect.exe. Sadly, this has made no difference. The first automated script of the day still generates the following email notification. From Retrospect: Script "MyPicsDuplicateToNAS" failed during automatic execution, error -1017 (insufficient permissions). Please launch Retrospect and check the log for details. The log simply repeats the same information. If Retrospect is already running in the foreground at the time this script is activated, the script runs to completion without any errors. I've no idea why there should be a permissions issue in one situation but not the other. That's not the only irritation. When I view the Dashboard after getting that error message, I am told that "Retrospect is currently running in the background. Click Launch Retrospect to stop any running executions and launch Retrospect", but clicking Launch Retrospect has no effect other than to display the message "Waiting for Retrospect to exit". The only way I can get the full version of Retrospect to run is to kill the first of two Retrospect processes listed in Windows Task Manager. It's all a bit of a mess . Any guidance would be much appreciated.
  12. Tech support told me that the bug remained unsolved as they had never previously been able to replicate it. However, it looks like they are planning to make another attempt.
  13. Retrospect tech support has now added the details of my problem to the following open bug. They didn't say how long it had been open, but I was told that they plan to run some tests using a Synology NAS. At present, they seem to think that the problem might be limited to the use of Synology devices, though your experience with Buffalo LinkStations suggests otherwise. Bug 5994 - Retrospect incorrectly matching unchanged files as changed when copying from NAS.
  14. Despite my lack of a support contract, Retrospect tech support acknowledged my bug report and requested a copy of my Operations_log.utx file. Time will tell if it generates any useful feedback or a software update.
  15. Thanks, David. I have now submitted a Support Case. However, I am not optimistic about a solution. Before finalising this support case, I made another check of the Retrospect Knowledge Base and found the following entry. It looks like this duplication bug has been present for over 6 years! ---------------------------------------------------------- Issues duplicating to NAS devices Resources One solution is to use the Backup option in Retrospect instead of Duplicate: When Retrospect performs a Backup the files are kept in a special way that only Retrospect can read and that way the files stay identical to the source even on the NAS device solving the issue of recopy files that all ready in the destination. Last Update: February 13, 2012
×