Tickets :: Comment on [#15080] ActiveSync only works in initial configuration

* Your Email Address
* Spam protection	Enter the letters below: . ..__..__ . ..__ \| \|\| \|[__)\| \|\| \ \|/\\|\|__\|\| \\|/\\|\|__/
Comment	>> Thanks for the hint - after setting the permission I got a litte further :) >> >> However I still have sync issues :-( >> >> What I have done: >> 1. Added permissions in horde-->permissions to access horde application >> 2. Remove the device from activesync configuration >> 3. deleted the .ost file from outlook to restart initialization, due >> to sync-id issues referred to in the logs >> >> After reinitializing everything Outlook started to download all the >> messages in all folders - that worked perfectly :) >> >> Then I sent a test message to my mailbox and hoped that it'll sync >> also - but it didn't. >> >> Skimming through the logs I found two issues: >> >> ######################################################################################## >> [8391][2022-01-23T07:39:48+00:00] NOTICE: STATE: Error saving state, >> checking if this is due to previous synckey >> {61ed0020-a9b8-4f22-a59c-20c59f45fb64}10 not being accepted by client. >> [8391][2022-01-23T07:39:48+00:00] O: </Folder> >> [8391][2022-01-23T07:39:48+00:00] >>>: Collection output peak memory >> usage: 2097152 >> [8391][2022-01-23T07:39:48+00:00] INFO: COLLECTIONS: Initializing >> state for collection: @Calendar@, synckey: >> {61ed0020-1d04-43e2-b600-20c59f45fb64}2 >> [8391][2022-01-23T07:39:48+00:00] >>>: STATE: Loading state for >> synckey {61ed0020-1d04-43e2-b600-20c59f45fb64}2 >> [8391][2022-01-23T07:39:48+00:00] >>>: STATE: Initializing message >> diff engine for A00722152 (@Calendar@) >> [8391][2022-01-23T07:39:48+00:00] >>>: >> Horde_Core_ActiveSync_Driver::getSyncStamp(@Calendar@, 1259); >> [8391][2022-01-23T08:39:48+01:00] >>>: STATE: Using SYNCSTAMP 1259 >> for A00722152. >> [8391][2022-01-23T08:39:48+01:00] >>>: >> Horde_Core_ActiveSync_Driver::getServerChanges(@Calendar@, 1259, >> 1259, 0, 0, 1, 100, ) >> [8391][2022-01-23T08:39:48+01:00] >>>: Fetching changes for calendar >> using MODSEQ. >> [8391][2022-01-23T08:39:48+01:00] >>>: Polling for SOFTDELETE items >> in calendar collection >> [8391][2022-01-23T08:39:48+01:00] ERR: Permission Denied >> [8389][2022-01-23T07:39:48+00:00] INFO: >> ----------Horde_Core_ActiveSync_Driver::authenticate() attempt for >> Stefan@graf-online.me---------- >> [8389][2022-01-23T07:39:48+00:00] INFO: ----------PING request >> received for user Stefan@graf-online.me >> [8389][2022-01-23T07:39:48+00:00] >>>: STATE: Device entry exists for >> 4C7CB7925B3442B59E878E5CC56280B4, updating userAgent, version, and >> supported. >> [8389][2022-01-23T07:39:48+00:00] INFO: ----------Request being >> handled for device: 4C7CB7925B3442B59E878E5CC56280B4, of type: >> WindowsOutlook15, supporting protocol version: 14.0, using >> Horde_ActiveSync v2.41.5 >> ########################################################################################### >> >> 1. There is an issue with the STATE as it cant be saved due to the client > This error is usually do to some activesync message/command being > sent to the client that it does not recognize or understand so it > sends the previous synckey back again to the server when asking for > changes. I can also be due to the client not receiving the response > due to some networking issue. > >> 2. There is a Permission Denied error in the calendar area > > Does the sync user have permissions to all the calendars being > requested in the sync? Not just permissions to the application, but > to each calendar. Sometimes this error is due to a stale preference > in Horde indicating which calendars to sync. You can try visiting the > sync preferences for kronolith and resetting/resaving the value for > which calendars to synchronize. > > >> I the added permissions for kronolith in the horde >> configuration-->permissions section. But this didn't help. >> >> Any suggestions what is missing? >> >> The attached log ist the full log of the sync attempt of outlook - >> starting right at the beginning and repeats where it got the issues. >> >> Thanks for your support! >> >> BR >> Stefan >
Attachment
Watch this ticket

Saved Queries