Tickets :: [#14004] Error 500 in communicating with ActiveSync server/unmatched end tag

6.0.0-beta1

8/12/25

Summary	Error 500 in communicating with ActiveSync server/unmatched end tag
Queue	Synchronization
Queue Version	FRAMEWORK_5_2
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	jonathan (at) tietznet (dot) de
Created	06/04/2015 (3722 days ago)
Due
Updated	06/22/2015 (3704 days ago)
Assigned	06/04/2015 (3722 days ago)
Resolved	06/19/2015 (3707 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/22/2015 07:40:45 PM	jonathan (at) tietznet (dot) de	Comment #7	Reply to this comment
At the same time, i saw 2 entries with the same email/id at the admin activesync device overview

06/22/2015 07:39:17 PM	jonathan (at) tietznet (dot) de	Comment #6	Reply to this comment
Hi, thanks for the screenshot. I also tried to that, but had trouble to disable SSL ;-) whatever But i managed to get the device talking via HTTP. At the same time, i saw 2 entries with the same email/id and deleted the oldest. Since then the error never occurred again. Same issue with 2 diffrent devices...

06/19/2015 02:09:16 PM	Michael Rubinsky	Comment #5 Summary ⇒ Error 500 in communicating with ActiveSync server/unmatched end tag	Reply to this comment
sigh I always seem to paste into the wrong field ... reverting the summary field.

06/19/2015 02:05:16 PM	Michael Rubinsky	Comment #4 State ⇒ Not A Bug Summary ⇒ Fantastic. Thanks for providing the trace screenshot, this removes any doubt - it is absolutely a client issue/bug. Closing, as there is nothing Horde can do to work around this - it' is100% broken WBXML.	Reply to this comment
Fantastic. Thanks for providing the trace screenshot, this removes any doubt - it is absolutely a client issue/bug. Closing, as there is nothing Horde can do to work around this - it' is100% broken WBXML.

06/19/2015 12:16:54 PM	horde (at) albasoft (dot) com	Comment #3 New Attachment: ActiveSync-Samsung-FolderId-ctrlA.png	Reply to this comment
Hi, I've experienced same issue, with Samsung S4. I've got that wiretrace of a connection and I've been able to verify that phone is sending no folderId. Attached is a screenshot of the decoded WBXML message. I have no idea when phone started with this, but every other activesync task seem to work correctly.

06/04/2015 06:51:34 PM	Michael Rubinsky	Comment #2 State ⇒ Feedback Assigned to Michael Rubinsky	Reply to this comment
[Show Quoted Text - 46 lines][Hide Quoted Text] Hi, with some Samsung devices we get some errors. 2015-06-04T18:32:40+02:00 INFO: [6921] Handling SYNC command. 2015-06-04T18:32:40+02:00 INFO: [6921] Checking policykey for device: xxx user: xxx 2015-06-04T18:32:40+02:00 INFO: [6921] Policykey: 0 verified. 2015-06-04T18:32:40+02:00 INFO: [6921] Creating new Horde_ActiveSync_SyncCache. 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <Synchronize> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <Folders> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <Folder> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <SyncKey> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I 0 2015-06-04T18:32:40+02:00 DEBUG: [6921] I </SyncKey> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <FolderId> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I 2015-06-04T18:32:40+02:00 ERR: [6921] Unmatched end tag: 2015-06-04T18:32:40+02:00 ERR: 2015-06-04T18:32:40+02:00 ERR: Protocol error same as http://horde.690.n7.nabble.com/syncing-with-Galaxy-S4-td118995.html mod_security_log: --e0d1f66b-B-- POST /Microsoft-Server-ActiveSync?Cmd=Sync&User=xxx&DeviceId=xxx&DeviceType=SAMSUNGGTN7000 HTTP/1.1 Authorization: Basic xxx MS-ASProtocolVersion: 14.1 Connection: keep-alive User-Agent: SAMSUNG-GT-N7000/100.40102 X-MS-PolicyKey: 0 Content-Type: application/vnd.ms-sync.wbxml Content-Length: 18 Host: xxx --e0d1f66b-C-- jE\OK0R --e0d1f66b-F-- HTTP/1.1 500 Internal Server Error --e0d1f66b-C-- are the post values are this enough infos or do you need more? The answer is the same as in the thread you posted a link to. It's a broken client request; the FOLDERID tag MUST contain a valid folder identifier. In this case, the client is sending an empty tag. If you are able to obtain a full wiretrace of the connection using a tool like wireshark, I can look to see exactly what WBXML is being sent to be sure I'm understanding the issue. Otherwise there is nothing else I can do. FWIW, I have both a stock Note 3 and a stock Galaxy S5 - neither of which exhibit this behavior.

06/04/2015 05:14:45 PM	jonathan (at) tietznet (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Error 500 in communicating with ActiveSync server/unmatched end tag Queue ⇒ Synchronization Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Hi, with some Samsung devices we get some errors. 2015-06-04T18:32:40+02:00 INFO: [6921] Handling SYNC command. 2015-06-04T18:32:40+02:00 INFO: [6921] Checking policykey for device: xxx user: xxx 2015-06-04T18:32:40+02:00 INFO: [6921] Policykey: 0 verified. 2015-06-04T18:32:40+02:00 INFO: [6921] Creating new Horde_ActiveSync_SyncCache. 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <Synchronize> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <Folders> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <Folder> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <SyncKey> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I 0 2015-06-04T18:32:40+02:00 DEBUG: [6921] I </SyncKey> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I <FolderId> 2015-06-04T18:32:40+02:00 DEBUG: [6921] I 2015-06-04T18:32:40+02:00 ERR: [6921] Unmatched end tag: 2015-06-04T18:32:40+02:00 ERR: 2015-06-04T18:32:40+02:00 ERR: Protocol error same as http://horde.690.n7.nabble.com/syncing-with-Galaxy-S4-td118995.html mod_security_log: --e0d1f66b-B-- POST /Microsoft-Server-ActiveSync?Cmd=Sync&User=xxx&DeviceId=xxx&DeviceType=SAMSUNGGTN7000 HTTP/1.1 Authorization: Basic xxx MS-ASProtocolVersion: 14.1 Connection: keep-alive User-Agent: SAMSUNG-GT-N7000/100.40102 X-MS-PolicyKey: 0 Content-Type: application/vnd.ms-sync.wbxml Content-Length: 18 Host: xxx --e0d1f66b-C-- jE\OK0R --e0d1f66b-F-- HTTP/1.1 500 Internal Server Error --e0d1f66b-C-- are the post values are this enough infos or do you need more?