[Tickets #13351] Re: Activesync Error 500: FOLDERUPDATE Unmatched end tag FolderHierarchy:ParentId

noreply at bugs.horde.org noreply at bugs.horde.org
Fri Jul 11 18:42:03 UTC 2014


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13351
------------------------------------------------------------------------------
  Ticket             | 13351
  Updated By         | software-horde at interfasys.ch
  Summary            | Activesync Error 500: FOLDERUPDATE Unmatched end tag
                     | FolderHierarchy:ParentId
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


software-horde at interfasys.ch (2014-07-11 18:42) wrote:

>> 2014-07-11T11:27:43+02:00 INFO: [BB1234ABCD] Handling
>> FOLDER[CREATE|DELETE|CHANGE] command.
>> 2014-07-11T11:27:43+02:00 DEBUG: [31538] I  <FolderHierarchy:FolderUpdate>
>> 2014-07-11T11:27:43+02:00 DEBUG: [31538] I   <FolderHierarchy:SyncKey>
>> 2014-07-11T11:27:43+02:00 DEBUG: [31538] I     
>> {5394b0ef-ba80-4f73-9261-945f904cae96}2
>> 2014-07-11T11:27:43+02:00 DEBUG: [31538] I   </FolderHierarchy:SyncKey>
>> 2014-07-11T11:27:43+02:00 DEBUG: [31538] I     
>> <FolderHierarchy:ServerEntryId />
>
> ^^^ Your client is sending an empty SERVERENTRYID tag. This is a  
> violation of the protocol. This is a REQUIRED value, and it makes  
> sense. A FOLDERUPDATE command makes absolutely no sense if the  
> client isn't telling the server WHICH folder we are updating.

Well, the problem is that it completely blocks the synchronisation of  
everything else for that account, so the user will stop getting emails  
because of a problem in Notes per example.
Isn't there a way to let the device know that there is a problem?

In this case, I even recreated the account on the device, but soon  
after the initial sync, the problem was back. I have no idea what is  
causing it.

I see 3 simlar sync keys in the state table which contain the synckey  
indicated in the logs, each with the sync_folderid set to foldersync.
Can I just remove them and get the device to resync folders?





More information about the bugs mailing list