Engine won't start and other problems

[toshy]

for a few days I have been having problems with my mac crashing during Retrospect operations (10.12.1 and retrospect 13.5). I was unable to resolve this and reverted to a different startup disk - not running Retrospect - and the crashes stopped. I repair a;; startup disks with dDiskwarrior and reverted to original startup disk. I used uninstaller (for version 10.5, cannot find more recent iteration) and reinstalled. Now the Engine will not start. I have tried safe boot and three different downloads for reinstalling Retrospect. No Joy. Any suggestions?

 

Thanks, Toshy

[twickland]

 I used uninstaller (for version 10.5, cannot find more recent iteration) and reinstalled. 

When you initially installed Retrospect 13.5, the installer should have placed a copy of the Retrospect 13.5 uninstaller script in the Applications/Retrospect folder.

 

I would try manually trashing the Retrospect app folder and /Library/Preference Panes/Retrospect.prefPane, and dragging the folder "Retrospect" from /Library/Application Support to the desktop. Then reinstall Retrospect.

 

If you are now able to enter the license code and access the engine, try quitting the Retrospect console and stopping the engine and dragging the Catalogs folder and the file Config80.dat from the Retrospect folder on your desktop to /Library/Application Support/Retrospect, as well as any public and private keys you may have created. 

 

Restart the engine, launch the console, and see if all is well. If it isn't, that would indicate that your configuration file Config80.dat is corrupt. In that case, if you don't have a good backup copy, you will need to recreate all your scripts, lists, and rules from scratch.

[toshy]

Thanks for your reply - very helpful.

 

In fact, I had managed to get Retrospect and the Engine sorted again, with a new download and install that did ask for my licence code - but it did not give me an Uninstaller.

 

I decided to re-create all my sources, scripts etc and rebuilt the media sets from the backup disks. This took the better part of 36 hours and the mac did not crash while all of these Retrospect operations - and other background tasks - were running. It had previously been crashing four or five times a day while Retrospect was running. But the crashes returned as Retrospect began to execute scheduled copies and backups. I wasn't watching when the crashes actually happened but it would seem to me that Retrospect was the cause.

 

I've run DiskWarrior 5 on all of the disks used for backups and it reports no problems.

 

I've now stopped the Engine and will let the Mac run overnight to see if I get any other crashes.

 

If Retrospect is the cause do you have any idea what the trigger is? I've got some of the crash reports but they don't mean anything to me :-(

 

Thanks for your help

[toshy]

I eventually had to reinstall system after wiping my disk. Now, Retrospect says that the catalog files for my backups are missing and gives a path for each as Library/Application Support/Retrospect/catalogs/media sets. And that is exactly where the catalog files are sitting. Can I make Retrospect recognise them or do I have to rebuild each 30gb catalog from scratch?

 

Thanks

[Lennart_T]

If you double click on the catalog files (in the Finder), then Retrospect should be able to recognize them again.

[rogerbil]

Thanks again. That worked but the backups listed so may errors that in the end I rebuilt the catalogs and now all is well. EXCEPt that one client is consistently unrecognised because of password 507 errors. I'm confused about client passwords. Should they match the password in Retrospect General preferences. If not, how do I make the clients visible to the backups

[Lennart_T]

You enter each client's individual password when you add the client. (The passwords may be the same, although they are, in fact, individual.)

 

So "Forget" the troublesome client and add it again should solve that problem.

[toshy]

Thanks again. I've tried this and when I attempt to add the client to the backup console the password field is always inaccessible and i get the 507 wrong password error. I've uninstalled and reinstalled the client software on the client machine, even removed the 'retro client state' preference on the client library, but the console will still not let me enter a password.

 

Does this suggest a corruption in the Backup machine's Retospect preferences? If so, which one and can I safely delete it>

 

Thanks for all of your help.

[Lennart_T]

Did you delete the correct client state file?

http://forums.retrospect.com/index.php?/topic/152276-password-incorrect/?p=262203

[toshy]

Thanks again. I eventually got Retrospect to add the client but still have problems. Only the client startup drive is recognised when I open the disclosure tab for the client machine. All of the other drives have an x or a tilde beside them even though All Volumes is checked in the Options tab of the console display. Selecting individual volumes in the console gives me a 1107 error, File/directory not found.

 

is this fixable?