When I sync with my .Mac or via Missing Sync it takes tops 3 minutes or so to sync.

If Daylite doesn't completely crash or hang during syncing, then right now for me it's taking well over 10 minutes and doesn't seem like it's working?

How about the progress bar? Is that suppose to actually indicate how long it might take? Does it work?

thanks

Kerry

Well it crashed so....
I'm still unable to actually try this program out.

Please definitely send us your Sync crash logs (a dialog should pop up asking you to send them) as they will help us narrow down solutions quickly.

As for sync time, it may take some time, as you have experienced, depending on the amount of data in particular.

The progress indicator is indeterminate, meaning that it shows you simply that work is happening; unfortunately we have no reliable way of calculating the time remaining.

HTH

Also, the first sync may take very long, but eventually it goes quite quickly after you start using Daylite day to day.

Techno, welcome to the wonderful experience of synching with DayLite's new and "improved" synching. 3 minute tasks now take hours. You cannot even cancel or quit the program or shutdown until it finishes. It will start "synchronizing" even when you merely CLICK on a contact in Contacts window, etc. And that is if you are LUCKY. Other times it will just crash - as you are no doubt finding out. Do a search on the word Synchronization and/or iCal/Addressbook and you will find other threads here of people who feel your pain. Thanks.

Imran

Imran

Regular visitors to this forum know that you have had some sync issues with Daylite, but to imply that your problems are common is disingenuous at best.

I, and many other people, do not have anything like the sync trouble you appear to have, and have found Daylite’s syncing to be rapid, trouble-free and generally work exactly as advertised. Any remaining issues I do have are because Daylite’s data structure is much more ‘rich’ than Sync Services’, and some of Daylite’s data simply won’t sync because it has nowhere to ‘go’.

Jumping into threads, whining about how you are having problems with sync—when hundreds of people are not—serves only to discourage other users from using the software where there is no need, make it seem like Marketcircle are producing poor software (when they blatantly are not), and finally make people less likely to actually try and help your issues.

Recent posts from yourself have gone from ‘I have been having trouble, how can I solve this’, to ‘this is a garbage upgrade and I shall actively warn people not to use it, just because I am having problems’. The first is a defensible stance, the second is not, and is simply petty and immature.

Please try and refrain from making baseless statements about the general stability and results of Daylite’s sync process; you may have problems, many of us do not. If you haven’t anything useful to add to a thread, try not posting at all.

I was going to write a similar response to Andy's but he saved me the trouble of a long post. I do not share Imran's experience at all. I know there are some issues being ironed out for a few people, but in general the new sync experience is a definite improvement and working well.

I do also hope the problems that Imran is having get solved soon! I know how frustrating this kind of thing can be.

I have been using the software for a couple of years and can tell you that overall MC has done a great job. However there is always room for improvement.

I too have had syncing problems. MC's support has not been helpful in terms of a resolution. In fact they do not always get back to you when they say they will.

The error I have been getting is:

Exception: NSInvalidArgumentException - [ISyncConjunctionFilter shouldApplyRecord:withRecordIdentifier:]: the record com.apple.syncservices:0C9F5A11-95B3-4428-98CD-233FC2EC224F should have an entity name, but instead it is {}

Could not get stack trace

After three weeks and paying for tech support from MC I finally decided to get help from Apple. The solution was to reset my sync history. Syncing works great now!

I guess MC does not have all the answers. I hope this helps someone.

Hi Dayliters,,

I have upgraded to Leopard on my imac and my Powerbook and followed the instructions to sync my database first. After the sync I went offline again on my Powerbook.

Next stopped and deleted the offline database with openbase manager. Then logged into the online database (located on my iMac) went offline. The offline database was created but it stopped when it reached "Large data" being synchronised. After some time I had to force quit daylight and checked the database with open base manager. It was there and running in the openbase manager but the seize was only 860 K.

Having seen in a post that that may take some time I started the cycle again (stop and remove database log into online database and go offline) left my Powerbook on and ran the process overnight for about 12 hours or more - still no progress and the progress bar just stayed in the same position and the beach ball was still on.

So force quit again and check the databse seize - again exactly 860K.

Another issue is now when I am logged into the online database from my Powerbook I am no longer able to log into the online databse on my server (iMac) - it syas too many user logged in buy another liscense. I do have 2 seats (one liscense for 2 computer) and only have Daylite installed on my iMac and my Powerbook.

I hope that some of you do have an idea how to solve - since I am sure that I am not the only one who is facing the transition problem.

I am in urgent need of a solution because I do depend quite a bit on daylite and need the offline database when I am travelling.

Thanks for help out there.

Best regards

Ralf

I am having some problems with the time it takes to synchronize. I have sychronizing happening automatically when I make changes and can be a bit slow but that isn't an insurmountable problem. When I quit the program does into synchronizing and takes a long time. It is doing it now. I don't understand why, as it seems to sync the orgs and contact that have been checked as I work? I would have thought it would simply do a last check before quitting but on quitting there is this prolonged Synchronizing transverse blue barber pole activity progress, working away and I can't tell whether the db is damaged or it is just going to take hours. This is not something that has happened before at quit, at least it certainly hasn't taken this long. Any ideas?