Search the Community
Showing results for tags 'Retrospect Client'.
Found 2 results
henry-in-florida posted a topic in Retrospect bug reportsMy client didn't run automatically because for some unknown reason, the Multi-cast shows as the port turned off after a normal restart and could not be re-enabled manually from the client's preferences. I had to do one of the following (chose the first one) to manually run a backup. Seems to happen whenever this laptop is taken away from the port used in a fixed set up on my LAN: Direct access entry port assignment instead of Multi-cast. Uninstall client and reinstall thereby re-opening the port. Remove the client at the engine or Retro Server and reinstall it there. I cannot see a way to troubleshoot the cause further. If anyone has ideas on this forum, please advise. I consider the above no more than work-arounds to the actual problem. I believe this problem goes back a long, long while. However this is the first time it has reared it's ugly head in a while.
Retrospect Client 10.5.0 (110) on Windows 10 Pro 64-bit 10586.14 I am submitting this to maybe assist others who encounter the same issues because AFAIK our Client system is “vanilla”. Windows 10 was clean installed on the Client, not as an upgrade. On the Client the Windows Event Viewer/Application log showed VSS 8194 “Errors” during Retrospect backup (ie not merely “Warnings” nor “Information”) This VSS issue was resolved by applying Rich_B_72’s solution . However then CAPI2 513 “Errors” became visible in the Client’s Windows Event Viewer/Application log during Retrospect backup. This CAPI2 issue was resolved by applying Fearless96’s version of the solution suggested by szz43.