Tickets :: [#14454] (Active Sync) No Errors in Log, but connections fail permanently

6.0.0-beta1

7/6/25

Summary	(Active Sync) No Errors in Log, but connections fail permanently
Queue	Synchronization
Queue Version	Git master
Type	Bug
State	Not Reproducible
Priority	1. Low
Owners
Requester	nstrix.paal (at) gmail (dot) com
Created	08/25/2016 (3237 days ago)
Due
Updated	09/12/2016 (3219 days ago)
Assigned	08/25/2016 (3237 days ago)
Resolved	09/12/2016 (3219 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09/12/2016 02:02:20 AM	Michael Rubinsky	State ⇒ Not Reproducible

09/01/2016 07:41:22 PM	Michael Rubinsky	Comment #5	Reply to this comment
My original comment still stands. The log shows the client asking for a foldersync after it downloads some email and attachment data. The foldersync responds normally, then the client asks to reset the hierarchy - which is probably what is causing you the issues. It's a client issue, probably triggered by some data being sent in a broken email.

08/30/2016 07:38:48 AM	nstrix (dot) paal (at) gmail (dot) com	Comment #4	Reply to this comment
Sorry, had to upload the Logfile here: http://www.file-upload.net/download-11895048/ANDROIDC1917531523.txt.html Thanks! [Show Quoted Text - 29 lines][Hide Quoted Text] Hi, as Mr. Wolf said, we've installed a clean Horde with PEAR (without this damn plesk). Syncing for one postbox works perfect! But two other won't "hold" the connection. First sync on these two postboxes work, but if you do anything it seems to disconnect. We now use the Horde Groupware 5.2.15 with the latest Active Sync .. Logs included. Thanks for your help!! Typically this is caused by some data in the email that the client doesn't like, like some non-utf-8 data. The log looks fine after a brief overview. I would suggest moving the email, one message at a time to see if you can find the troublesome message. Start with the messages that are listed last in the log (there are a group of 4 of them that appear in the last sync response). If you find the email, and are able to share it with me I can try to figure out what the actual trigger was. Otherwise, not much I can do, since this is the client deciding to re-negotiate it's sync state with the server.

08/30/2016 07:36:25 AM	nstrix (dot) paal (at) gmail (dot) com	Comment #3	Reply to this comment
Hi, as Mr. Wolf said, we've installed a clean Horde with PEAR (without this damn plesk). Syncing for one postbox works perfect! But two other won't "hold" the connection. First sync on these two postboxes work, but if you do anything it seems to disconnect. We now use the Horde Groupware 5.2.15 with the latest Active Sync .. Logs included. Thanks for your help!! [Show Quoted Text - 13 lines][Hide Quoted Text] Typically this is caused by some data in the email that the client doesn't like, like some non-utf-8 data. The log looks fine after a brief overview. I would suggest moving the email, one message at a time to see if you can find the troublesome message. Start with the messages that are listed last in the log (there are a group of 4 of them that appear in the last sync response). If you find the email, and are able to share it with me I can try to figure out what the actual trigger was. Otherwise, not much I can do, since this is the client deciding to re-negotiate it's sync state with the server.

08/25/2016 03:42:44 PM	Michael Rubinsky	Version ⇒ Git master Queue ⇒ Synchronization

08/25/2016 03:42:27 PM	Michael Rubinsky	Comment #2 Priority ⇒ 1. Low State ⇒ Feedback	Reply to this comment
Typically this is caused by some data in the email that the client doesn't like, like some non-utf-8 data. The log looks fine after a brief overview. I would suggest moving the email, one message at a time to see if you can find the troublesome message. Start with the messages that are listed last in the log (there are a group of 4 of them that appear in the last sync response). If you find the email, and are able to share it with me I can try to figure out what the actual trigger was. Otherwise, not much I can do, since this is the client deciding to re-negotiate it's sync state with the server.

08/25/2016 08:05:53 AM	nstrix (dot) paal (at) gmail (dot) com	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ (Active Sync) No Errors in Log, but connections fail permanently Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No New Attachment: ANDROIDC1917531523_2.txt State ⇒ Unconfirmed	Reply to this comment
Hi, we've configured our active sync and got it to work. No we have the problem that the Android Devices connect to the server but then close the connection and try to reconnect permanently. Logs are included. Thanks for help!!