Duplicates in NUD when syncing Treos on a network

Posted by: tsc

Duplicates in NUD when syncing Treos on a network - 02/03/08 05:33 PM

We are on a network: 3 desktops (G5, G4 and imac G4), 2 mac laptops, 2 palm Treo 700ps. Everything is on Leopard except the imac and the slowest desktop, a G4, which are running 10.4.11. The G4 is also running the NUDC server. We use categories and sets. The Treos are a new addition to our workflow and we're really excited to be taking our calendar, to do lists, etc., with us. Very Happy However, there's a big problem. Whenever we sync, many of the appointments are duplicated on the server calendar (and on the Palm). Crying or Very sad These duplicates come on the server calendar in that person's category color. On the server calendar, it doesn't work to merge or delete duplicates.

What is causing this? How do I fix it? Question Our calendar is way too complex to keep deleting these extra events by hand, and it has absolutely mangled our calendar history.
Posted by: dnorcross

Re: Duplicates in NUD when syncing Treos on a network - 02/04/08 09:31 AM

Originally Posted By: "tsc"

We are on a network: 3 desktops (G5, G4 and imac G4), 2 mac laptops, 2 palm Treo 700ps. Everything is on Leopard except the imac and the slowest desktop, a G4, which are running 10.4.11. The G4 is also running the NUDC server. We use categories and sets. The Treos are a new addition to our workflow and we're really excited to be taking our calendar, to do lists, etc., with us. Very Happy However, there's a big problem. Whenever we sync, many of the appointments are duplicated on the server calendar (and on the Palm). Crying or Very sad These duplicates come on the server calendar in that person's category color. On the server calendar, it doesn't work to merge or delete duplicates.

What is causing this? How do I fix it? Question Our calendar is way too complex to keep deleting these extra events by hand, and it has absolutely mangled our calendar history.


Duplication during/after a sync is caused by the desktop and Treo data files not recognizing each other properly. It results, as you have experienced, in duplication of the events. And, since the files did not recognize each other properly to begin with, they do not recognize the events as duplication. We suggest regularly setting the Now Up-to-Date conduit to 'overwrite handheld'. Doing that at least weekly helps keep the data files communication correctly. If events are not normally entered on the Treo, you may want to consider making 'overwrite' the default.
Posted by: tsc

Re: Duplicates in NUD when syncing Treos on a network - 02/04/08 11:23 AM

Thanks -- I'll try it. I just tried to open NC and it said that it couldn't open because a preference file couldn't be created. Never had THAT happen before. Any quick fix for that before I go searching?
Posted by: dnorcross

Re: Duplicates in NUD when syncing Treos on a network - 02/04/08 11:49 AM

Originally Posted By: "tsc"

Thanks -- I'll try it. I just tried to open NC and it said that it couldn't open because a preference file couldn't be created. Never had THAT happen before. Any quick fix for that before I go searching?


It is a problem with the existing Now Contact program prefs. Try the following:

1. Make sure you know where your primary contact file is stored on your hard drive. You'll need to know where it is to set it as your primary file again at the end of this process.
2. Quit Now Contact (if it is running).
3. Open a new Finder window and select Home from the Go menu.
4. Once in your Home folder, go to: /Library/Preferences/
5. Find the files named com.nowsoftware.nowcontact.plist and com.poweronsoftware.nowcontact.plist and move them to the desktop.
6. Find the folder named Now Contact Prefs and move it to the desktop as well.
7. Open your Now Contact file and make it your primary contact file (Launch Now Contact, open the File menu, select Open, make sure there is a checkmark next to the option "Make this my primary file," locate your Now Contact file, highlight it and click Open).
8. Trash the items moved to the desktop in steps 5 and 6.