Mobile home syncing problem

Question

Hi all,
I have a mobile home syncing problem. When the sync runs it returns the following error:
Unknown error: -[SStore myNodeForNode:isDestNode:]: Unable to find node for "Pictures/iPhoto Library/Data/2008/6-Aug-08/DSC00042.jpg" in store "HomeSyncMirrorPeer-DfrxJp1ET07-zivj" Please try again later. If this problem persists, contact your network administrator.
This file does not exist both on the server and on my mobile laptop.
Any ideas how to solve this?
Thanks,
Ziv

Answer 1

Shawn,
I've done the deletion of those folders a number of times, with no luck.
The most recent attempt to get this to work was:
1. Delete ~/.FileSync and ~/Library/FileSync from the server machine.
2. With a brand-new install of OS X on a laptop, create a local administrator, join the server, then login as the user account that wants a mobile account
3. Look at logs
I still get an exception on the server
0:: \[10/07/31 13:39:47.791\] EXCEPTION: Unknown error 2002 <-\[SNetworkReachabilityMonitor init\] (NetworkReachabilityMonitor.m:72): "(Error Domain=com.apple.SystemConfiguration Code=2002 UserInfo=0x10027adc0 "The operation couldn<E2><80><99>t be completed. (com.apple.SystemConfiguration error 2002 - Configuration daemon not (no longer) available)")">
0:: \[10/07/31 13:39:47.791\] USERINFO: {
0:: \[10/07/31 13:39:47.791\] NSDescription = "Configuration daemon not (no longer) available";
0:: \[10/07/31 13:39:47.791\] }
0:: \[10/07/31 13:39:47.791\] BACKTRACE: {
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x100014831
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x100014688
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff82ffb535
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff8300963e
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff83001eaa
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x7fff82ffa1ba
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x1000036c3
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x10007f4e0
0:: \[10/07/31 13:39:47.791\] ?<C2><A0>|<C2><A0>0x2
0:: \[10/07/31 13:39:47.791\] }
0:: \[10/07/31 13:39:47.792\] Bye (PID:38660)
as well as the corresponding error on the client.
I'm quite frustrated with the whole situation at this point. I'm sure some folks have gotten it to work, but since it has exceptions like this silently, it slowly corrupts the data in an account. I still want to get it to work, but am skeptical that it will.
Message was edited by: Benjamin Kuperman