The Omni Group
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!

Go Back   The Omni Group Forums > OmniFocus > OmniFocus Syncing
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Unable to read document. Thread Tools Search this Thread Display Modes
Unable to read document.

No root can reach all tail transactions in "".

Help! When I try to set up sync through preferences, this is the message I get. I know that I've probably corrupted something. I wasn't aware of the warning about MobileMe and other data conflicts.
I just started getting this same error this morning, from both the desktop & iphone app. I can provide http logs, tcpdumps, etc from the server if it's helpful to anybody.
I decided to move the omnifocus database on the DAV server aside, so i'm good now.
I have the same issue. OmniFocus on the Mac syncs fine with MobileMe, but the iPhone client gives the message above. The data file on idisk must be OK, as the Mac is syncing with it - so why is the iPhone failing? I have tried a database reset and resync, but get the same message again.
Fixed :)

Shared sync settings from the Mac again and all worked fine. Not sure why!

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Similar Threads
Thread Thread Starter Forum Replies Last Post
Error Message: Unable to read document, help please javimazzaf OmniFocus 1 for Mac 2 2012-10-19 01:40 PM
Unable to read document, etc. Brenko iDisk/MobileMe/.Mac Syncing 2 2010-10-15 01:24 PM
Unable to read document: Transaction identifier...contains “ ” DWS OmniFocus 1 for Mac 3 2009-10-30 05:54 AM
Unable to read document ehamburg OmniFocus for iPhone 2 2008-07-11 10:30 AM
Unable to read document -- No root transactions found ewits OmniFocus 1 for Mac 1 2008-02-14 04:56 PM

All times are GMT -8. The time now is 11:24 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.