PDA

View Full Version : "Sync Server" error during backup


EddieC
05-24-2006, 04:03 PM
I have recently been experiencing a problem which has prevented me from using SD! successfully.

Basically any backup that I try to perform results in an error mesage that reads " A Sync Server is already running on this computer, exiting process." in the console.log. This always happens a short time into the backup, after repairing permissions. Additionally, Carbon Copy Cloner has no trouble performing a full backup.

I have done a search and the only thread I could find offered a suggestion to 'Archive & Install' the OS. I have done this but the problem still persists.

Any help or suggestions will be greatly appreciated.

dnanian
05-24-2006, 04:14 PM
Hi, Eddie. The SyncServer message in the console is pretty common, and doesn't have much to do with SuperDuper: rather, it simply means that iSync has tried to autolaunch its sync server, and has found one already running.

So -- what's happening in SuperDuper itself? Is the backup completing fine?

EddieC
05-24-2006, 05:10 PM
Thanks for replying, Dave.

Alas SD! stops and does not complete the backup at that point.

dnanian
05-24-2006, 06:30 PM
And what does SD say in its log?

EddieC
05-24-2006, 08:34 PM
I've managed to resolve the problem. Apparently there were problems with a folder of documents (which I don't need, but cannot delete for now). I simply created a script to ignore that folder and I have now managed to perform a complete backup with SD!

Thank you for your patience.

dnanian
05-24-2006, 09:32 PM
Ah, good. Truly, it has nothing to do with the Sync Server message you received. But, SD! should tell you exactly what file(s) are having trouble, and by following the Troubleshooting section of the User's Guide, you should be able to determine what's wrong, and what has to be removed and/or replaced.

EddieC
05-25-2006, 03:41 AM
Thank you. I realise that Sync Server was unrelated now.

I managed to locate the problem folder/files by looking in the SD log. There was an error that prevented the files from being read. Now that I know where to look, I'll be better prepared for any future problems.

Thanks once again.

dnanian
05-25-2006, 07:29 AM
Great, Eddie -- glad you're all set. Thanks for the follow-up! :)