Jump to content

hevanw

Members
  • Content count

    26
  • Joined

  • Last visited

  • Days Won

    2

hevanw last won the day on May 21

hevanw had the most liked content!

Community Reputation

3 Neutral

About hevanw

  • Rank
    Member

Recent Profile Visitors

183 profile views
  1. hevanw

    Error -1103 after Windows 10 April Update

    Excited to report that I got my Retrospect backups fixed now as well !! So, disabling the "Save space and download files as you use them" setting did not work for me. So in addition to that, I tried disabling OneDrive altogether (Unlink PC/account and then remove the entire OneDrive folder) and then linking my account again which then again downloaded all files. The next Retrospect scheduled (proactive actually) run then succeeded with 0 errors or warnings ! This worked now on 2 machines already, so will try kids laptop next, but pretty confident this will work as well. Thanks to the folks active in this thread !
  2. hevanw

    Error -1103 after Windows 10 April Update

    Thanks! I can confirm that OneDrive is a real folder, not a reparse point (tried both your methods). However, your second method does not yield 'File Not Found' but a bunch of other folders under my homedir: Application Data, Cookies, Local Settings, etc.... which all show up as <JUNCTION>. Also, I'm the only user on this specific machine so I'm certain there are no other OneDrive folders. I'll give Lucky_Phil's approach a try though.
  3. hevanw

    Error -1103 after Windows 10 April Update

    I hate it when something solves the problem for everyone except myself :). I still have the problem, but can confirm it's also related to OneDrive here. If I exclude the OneDrive folder in my Selector, then the backup does complete fine. Weird thing is that I still did get a -1103 error and it's related to OneDrive still. I see a bunch of the following lines all pertaining to different OneDrive folders [*] stfiDoBackupOne: error -1103 (write protected) on C:\Users\henkv\OneDrive\Documents\Manuals And then get the error: Trouble reading files, error -1103 (write protected) 9/5/2018 11:23:43: Trouble copying folders, error -1103 (write protected) ddex=69,985 EDIT, driving me crazy. The last couple hours all backups again aborted during scanning without a single file being backed up. This is with the OneDrive folder excluded from the selection. The error does not even show much : Scanning incomplete, error -1103 (write protected) 9/5/2018 16:44:26: Compressing catalog file EDIT2: whether it's the scan that aborts or the actual backup appears to be pretty random.
  4. hevanw

    Error -1103 after Windows 10 April Update

    Ugh, thought this fixed the issue for me as well, but I still see an error -1103...
  5. hevanw

    Error -1103 after Windows 10 April Update

    Also updated the kids' laptop to April Update now and also there Retrospect Client is now broken. Interestingly though, the problem has changed apparently. While initially the error occurred during scan, as you can see from my OP, the problem now is happening during the actual backup. So a subset of files does get backed up, but then the backup aborts, with the following error. Trouble reading files, error -1103 (write protected) 5/5/2018 12:43:08: Execution incomplete Remaining: 224172 files, 36.0 GB Completed: 13900 files, 2.4 GB Performance: 388.2 MB/minute Duration: 00:10:57 (00:04:43 idle/loading/preparing) EDIT: browsed through my logs, and so apparently now it's my Surface Pro that does manage to do scans but aborts during backup. My old netbook and the kids' laptop still abort during scanning and don't backup a single file.
  6. hevanw

    Error -1103 after Windows 10 April Update

    When you say interactively, do you mean using 'immediate backup' ? Also, is that a local backup or a backup of a remote machine ? I just tried 'immediate backup' on my server to backup my client device, and I'm again getting the -1103 error.
  7. hevanw

    Error -1103 after Windows 10 April Update

    According to Support, the Error Event that I posted above, is not related to the issue and is something that can happen and can be ignored. This indeed seems to be correct since on my Netbook I am not seeing that Event, even though the backup fails in exactly the same way. I'll now try on my Netbook to install the full Retrospect version and see if I can make a backup locally.
  8. hevanw

    Error -1103 after Windows 10 April Update

    That's what I did on my very old AMD E-450 netbook. Wiped all the partitions and did a fresh re-install, and the backup is not working with Open Files Backup enabled. The other machine I have the problem with, is the first machine on which I did the April Update and that's my Surface Pro 3 with an i7-4650u. I have two more machines at home from wife and the kids, but those are still on the previous Windows 10 build. I'll try the kids' laptop next to see what that gives. I have also submitted a Support Case and they have confirmed they have seen it with other customers already as well. So I assume they are investigating it and I have provided them log files. Just hope the fix does not require a new release and I'll be forced to pay for an upgrade to v15. PS: are we all talking about client-server backups ? Or do some folks have an issue also with a local backup ? For me, the local backup of the Server is working fine, even though I would suppose that Retrospect Desktop would require the same permissions as the Retrospect Client would need. So that would indicate the permissions problem is limited to Retrospect Client.
  9. hevanw

    Error -1103 after Windows 10 April Update

    I don't think that's what's happening, or I may be misunderstanding you. I just did a complete fresh install of an old laptop from scratch to Windows 10 April Update, and I'm having the problem also with this laptop. So it's not a matter of permissions disappearing upon doing the April Update, because the problem is also there with a fresh install.
  10. hevanw

    Error -1103 after Windows 10 April Update

    I'm glad to hear there is a workaround even though it will not backup open files, but that's good enough for now. Thanks! So it's weird that your Event Log does not show anything... Don't know if you saw my post above, as I indeed do have error events pertaining to VSS. Also, my client machine where I have the problem happens to have been fully reinstalled as well on Dec 20 last year.
  11. hevanw

    Error -1103 after Windows 10 April Update

    Thanks for the suggestion, but it did not work, and neither did I expect it to work : 1. All catalog files are stored at server side. And the catalog files of all clients are in that same Documents folder. 2. The problem only occurs with a client that has upgraded to the April Update. 3. The abovementioned Error Event is also observed at the Client side. I'll go file a Support Case as David suggested.
  12. hevanw

    Error -1103 after Windows 10 April Update

    At each run of the Retrospect backup, I can see 6 occurrences of the following event in the Event Viewer on my client : Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requestor process. Operation: Gathering Writer Data Context: Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer Instance ID: {9c98913d-3b48-4c53-9a0a-14b72efc38cb}
  13. I have upgraded both my server and client machine to Windows 10 April Update (v1803). Since then my client cannot be backed up anymore. The error that I'm getting in the Operations Log at server side is this : Scanning incomplete, error -1103 (write protected) I already tried uninstall and reinstall of the client, but to no avail. I still have some combo's that do work: * The Server can still backup it's own filesystem (local backup) * The Server can also still backup a client machine that did not get the Windows 10 April Update yet. EDIT: I'm using Retrospect 12.6, not yet 15. EDIT2: I actually just noticed that the Windows services only has 2 Retrospect services anymore: Retrospect Client and Retrospect Instant Scan. I'm fairly certain that there also used to be a Retrospect Helper service in the past. Not 100% sure whether it disappeared as a result of the April Update.
  14. hevanw

    Error -530 (backup client not found)

    I think I'll indeed open a support case. I think I have found a workaround that is a bit better than reinstalling. This morning again wife's laptop could not be found. What fixed it though is restarting the Retrospect Client service in Windows. So for some reason, after a while (can be couple days, can be months) the service gets in a corrupt state. The weird thing is that shutting down and restarting the laptop, does not fix it. But at the moment I may not have enought test data to be certain about the cases in which the problem occurs and can be fixed.
  15. hevanw

    Error -530 (backup client not found)

    I'm still having the problem, but it now clearly looks like a Windows Firewall problem. It worked fine for several weeks. Then suddenly on Jan 18, I notice that my wife's laptop hasn't been backed up for several days. Again the same problem and nothing fixes it, except for reinstalling the client. 2 days later, both my own laptop as well as my wife's stop being backed up. Looking in the Server now both clients are not being found anymore. Pretty sure that reinstalling the client would fix it again. Did some testing now : * When I go to Clients->Add.. I can still see the backup clients under both Multicast as well as Subnet Broadcast. * Yet, when selecting them and doing Add, I will get a "-530 (backup client not found)". * More interesting is that the behavior changes when I turn off the Windows Firewall on the client. Then the error turns into a "-541 (backup client not installed or not running)". Yet, the client is installed, and I can open its config. Also both the Retrospect Client and Retrospect Instant Scan services are running. * If I turn off the Windows Firewall on the server, it's still the -530. * HOWEVER... if I turn off the firewall on both Client and Server, I almost immediately get the client popup that Retrospect is about to backup my files, i.e. the Proactive backup starts almost immediately and thus the Retrospect client can be found. Now need to figure out what happens with Windows Firewall that after a while it suddenly seems to start blocking Retrospect stuff. EDIT: apparently not that straightforward... When I turn off Firewall on all 3 devices, it fixes the backup of my own laptop, but not my wife's. EDIT2: also interesting, once my own laptop was found again by Retrospect (by turning off Firewall), I can again turn on the Firewall on both server and client and Retrospect keeps working... Makes no sense.
×