I see that at least one person with this problem is running Snow Leopard, but I also note that a number of us, myself included, are still using 10.5.8. Are you sure this is not at the root of the problem?
Just to say: this will be awesome once it works and the growing pains are over!
Same here. No Sync Group.
Got 2.05. Got the bundle. Installed a test database, but that didn’t create a sync group. Stopped the Firewall. Didn’t work.
I’m located in the Netherlands.
I haven’t tested this Greg, but you may want to look into Intego (it’s (virus/spam/etc) protection software). intego.com/
Nothing wrong with the software but I’ve had problems with it before in relation to other applications. I have Virusbarrier X6.
There are extra settings for the Firewall in there. My Firewall is set to “no restrictions”.
Those of you who are missing the Sync group: Is anything on the Console when loading DEVONthink that sounds alarming, such like the Sync Agent plugin not loading or any other error message? If yes, please send a quick email to bugs (at) devon-technologies.com.
Will do, and here it is in case it’s useful on this forum.
10/28/10 1:07:45 PM DEVONthink Pro Connection to devongetd failed. 10/28/10 1:09:33 PM DEVONthink Pro Error loading /Applications/DEVONthink Pro.app/Contents/PlugIns/Sync Agent.bundle/Contents/MacOS/Sync Agent: dlopen(/Applications/DEVONthink Pro.app/Contents/PlugIns/Sync Agent.bundle/Contents/MacOS/Sync Agent, 265): no suitable image found. Did find:
/Applications/DEVONthink Pro.app/Contents/PlugIns/Sync Agent.bundle/Contents/MacOS/Sync Agent: unknown required load command 0x80000022
Any idea of a timetable for 2.0.6? I can’t switch away from Leopard right now for a series of complicated reasons, so I’m hoping it will be soon!
I posted a longer message in the previous page, so I will be brief here. I have a sync group in all databases but one. If I start a new database I have a sync group. The sync group disappeared from the my most used database when I “ungrouped” it after realizing syncing a large database all at once was a bad idea. All I want to do now is get the sync group back to my primary database. Again: there is a sync group in ALL other databases as well as any new ones I create.