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

noreply at bugs.horde.org noreply at bugs.horde.org
Tue Aug 30 07:38:48 UTC 2016


BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14454
------------------------------------------------------------------------------
  Ticket           | 14454
  Aktualisiert Von | nstrix.paal at gmail.com
  Zusammenfassung  | (Active Sync) No Errors in Log, but connections fail
                   | permanently
  Warteschlange    | Synchronization
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


nstrix.paal at gmail.com (2016-08-30 07:38) hat geschrieben:

Sorry, had to upload the Logfile here:  
http://www.file-upload.net/download-11895048/ANDROIDC1917531523.txt.html

Thanks!


> 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.
>






More information about the bugs mailing list