Jump to content

haggis999

Members
  • Content count

    166
  • 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. Thanks for that information. I have exactly the same errors in my retroISA_log.utx file. I will just live with this problem for the time being, as I can't yet justify the expense of upgrading. It's been quite some time since a new version included features of any interest to me.
  2. I spoke too soon. Today's scheduled backup job for My Documents has once again generated a log containing the warning "Unable to use Instant Scan for My Documents on MyData1 (G:)". The RetroISAScans folder contains three .DAT files, two of which were overwritten by today's new scan. The smallest one (23kb) still carries yesterday's date. What might be causing this behaviour?
  3. That link prompted me to check my C:\ProgramData\RetroISA\RetroISAScans folder. It was empty, which suggested that Instant Scan has never previously worked for me, even though the RetroInstantScanService was running. However, stopping and restarting that service did the trick. Running one of my scripted backup tasks caused the first scan to take place of the My Documents folder and running it again used this scan info to shorten the backup process. Many thanks for pointing me in the right direction ?
  4. Instant Scan is enabled in the Preferences for my installation of Retrospect 12.6.1.101, but I have only just noticed that the logs for my scheduled backup jobs have contained the warning "Unable to use Instant Scan for My Documents on MyData1 (G:)" for well over a year (I really must need new glasses). G: is a local NTFS drive on the same Windows 10 PC as Retrospect. How do I fix this?
  5. haggis999

    Retrospect Launcher service not working

    I've never heard the term 'home lab' before, but a Google search provided some enlightenment from a variety of USA-based sources. Here in the UK, we think of 'laboratories' as places where research chemists in white coats carry out their experiments. We would not normally use that word for a computer room. For Brits, any reference to a 'lab' usually means a labrador dog! When I get some time, I might try experimenting with Synology's Active Directory Server package. I don't have any obvious need for multiple user accounts with varying privileges, but perhaps it provides a way to get around the restrictions mentioned by Scillonian and could thus make my Retrospect Launcher service work more reliably.
  6. haggis999

    Retrospect Launcher service not working

    I'm guessing that your reference to AD means a Microsoft Active Directory. If so, then that certainly makes your environment a little different from mine. I'm just a home-based user with my own private local network. If you are using Active Directory, I assume it means you are running under Windows Server. As Scillonian pointed out above on 1 June, Windows Server will tolerate a user instance to access a network resource with more than one set of credentials at any one time. That is not the case for my consumer version of Windows 10, and this is the limitation that I strongly suspect lies behind the rather unreliable behaviour of the Retrospect Launcher Service. Most of the time it works, but I still get the -1017 error about every week or so.
  7. 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.
  8. 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.
  9. 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.
  10. 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
  11. 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.
  12. 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
  13. 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.
  14. 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
  15. 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.
×