-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ActiveSync protocol violation error #24
Comments
Could you disconnect the failing account in TbSync Account Manager, enable the debug Log (@ Help) and reconnect again and send me the debug log? It does not contain any passwords but your contact and appointment data and your user name. I need the full debug log, because your "user data" is the reason for the error, which somehow breaks the XML, so I cannot parse it correctly. You can send the log directly to my email address. Thanks for your time |
Can you retry with the latest beta TbSync v0.6.8.3 (2017.12.28) ? Can i have a debug log of when that error happens? |
Cannot fix this without proper debug log. Added better error identification, so XML parse errors now have a dedicated error message with instructions on how to help me to fix this bug. |
probably fixed in v0.7.1 |
Fixed for me. Thanks very much! |
Please update your beta version of TbSync to 0.7.6.8 or any later version available at the release page. This version now includes an update notification, so I no longer have to contact all beta users, to update their TbSync versions: https://raw.githubusercontent.com/jobisoft/TbSync/master/screenshots/update_notification.png While on the beta release channel, I strongly suggest to update, if a newer version is available. Once a new stable version gets released, you automatically switch back to the stable release channel (you no longer receive update notifications for beta versions). |
My initial sync fails with the following error:
Error console shows:
XML Parsing Error: not well-formed
Location: moz-nullprincipal:{b20fc7a0-92aa-4b25-bd74-b829c3a50157}
Line Number 37, Column 12482: {b20fc7a0-92aa-4b25-bd74-b829c3a50157}:37:12482
The text was updated successfully, but these errors were encountered: