Active-Sync: Fehler beim Syncen mit "Invalid request content type"

renke

Junior Member

Join Date: Jul 2010

Posts: 4
- Share
- Tweet
#1

Active-Sync: Fehler beim Syncen mit "Invalid request content type"

02-24-2014, 05:02 PM

Hallo,

wir haben ein Problem bei der Inbetriebnahme des EAS auf unserem OX-Server - grundsätzlich sieht alles gut aus (Kommunikation vom Mobilgerät über den MDM-Proxy und den EAS-Dienst von OX bis zur IMAP-Authentifizierung), aber das Syncen schlägt fehl mit einer Exception vom Typ Invalid request content type application/vnd.ms-sync.wbxml.

Unsere Landschaft sieht folgendermaßen aus:

Mobile Device (hier: iphone) -> MDM von Sophos über einen reverse proxy -> OX-Server

OX ist auf dem Stand 7.4.2-6, installiert nach http://oxpedia.org/wiki/index.php?ti...allation_Guide

Im EAS-Debug-Log sieht alles so weit gut aus, der Server kann dann jedoch die Requests wohl nicht parsen, aus mir unklarer Ursache.

Irgendwelche Ideen, was bei uns schief läuft?

Danke & Grüße

-------------------------------------------------------
Sync-Lauf im EAS-Debug-Log

2014-02-20 10:04:49.839: 9b5f3a3d-3215-495d-9289-87a0eee25ce6 --- POST: username(46.115.xx.xx) application/vnd.ms-sync.wbxml, application/vnd.ms-sync.wbxml ---
<?xml version='1.0' encoding='utf-8' ?>
<FolderSync>
<SyncKey>0</SyncKey>
</FolderSync>
2014-02-20 10:04:49.840: 9b5f3a3d-3215-495d-9289-87a0eee25ce6 --- Outgoing result: application/vnd.ms-sync.wbxml ---
<?xml version='1.0' encoding='utf-8' ?>
<FolderSync>
<Status>10</Status>
</FolderSync>
3:64:username:EAS:ApplJJ125RRDA4S: FolderSync executed in 226 ms, no OX calls made.
2014-02-20 10:04:50.463: 29332815-fe45-4d0d-8fb8-87df296ad690 --- POST: username(46.115.131.164) application/vnd.ms-sync.wbxml, application/vnd.ms-sync.wbxml ---
<?xml version='1.0' encoding='utf-8' ?>
<Settings>
<UserInformation>
<Get />
</UserInformation>
<DeviceInformation>
<Set>
<Model>iPhone3C1</Model>
<OS>iOS 7.0.4 11B554a</OS>
<OSLanguage>de</OSLanguage>
<FriendlyName>Schwarz iPhone 4</FriendlyName>
</Set>
</DeviceInformation>
</Settings>
2014-02-20 10:04:50.464: 29332815-fe45-4d0d-8fb8-87df296ad690 --- Outgoing result: application/vnd.ms-sync.wbxml ---
<?xml version='1.0' encoding='utf-8' ?>
<Settings>
<Status>2</Status>
</Settings>
3:64:username:EAS:ApplJJ125RRDA4S: Settings executed in 0 ms, no OX calls made.

-------------------------------------------------------
Der gleiche Zeitraum im open-xchange.log

Login:username IP:46.115.x.x AuthID:ef0dfb55-6626-41d0-b025-666bc0b76098 Agent:Open-Xchange USM HTTP Client Client:USM-EAS(7.4.1-11-af1395448c7de3f818875cbaf16e891e8393394f- 6245) Interface:HTTP_JSON Context:3(3,defaultcontext,sys3) User:64(username) Session:3fc51235003f41718e61737c8880cb07 Random:56d7eb7c1689460f833b272318894f86
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .executeMethodOnce(OXJSONAccessImpl.java:537)
com.openexchange.ajpv13.remoteAddress=127.0.0.1

RESULT: OX Result: {"context_id":3,"session":"3fc51235003f41718e61737 c8880cb07","locale":"de_DE","user_id":64,"user":"u sername"}
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .login(OXJSONAccessImpl.java:180)
com.openexchange.ajpv13.remoteAddress=127.0.0.1

-1:-1:username:EAS:ApplJJ125RRDA4S Logged in, session id = 3fc51235003f41718e61737c8880cb07
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .obtainConnectionData(OXJSONAccessImpl.java:453)
com.openexchange.ajpv13.remoteAddress=127.0.0.1

-1:-1:username:EAS:ApplJJ125RRDA4S Retrieving OX session with ID: OX session 3fc51235003f41718e61737c8880cb07
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .doGet(OXJSONAccessImpl.java:329)
com.openexchange.ajpv13.remoteAddress=127.0.0.1

-1:-1:username:EAS:ApplJJ125RRDA4S GET http://localhost/ajax/config/
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .executeMethod(OXJSONAccessImpl.java:783)
com.openexchange.ajpv13.remoteAddress=127.0.0.1

GET/ajax/config/&session=3fc51235003f41718e61737c8880cb07&timezone =UTC
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .executeMethodOnce(OXJSONAccessImpl.java:537)
com.openexchange.ajpv13.remoteAddress=127.0.0.1

RESULT: OX Result: {"data":{"contact_id":63,"calendarnotification":tr ue,"beta":true,"participants": <snip>
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.ox_json.impl.OXJSONAccessImpl .getConfiguration(OXJSONAccessImpl.java:194)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.database.schema=oxdatabase_7

-1:-1:username:EAS:ApplJJ125RRDA4S Retrieved OX ajax configuration
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.database.ox.OXDBService.getRe adOnly(OXDBService.java:119)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.database.schema=oxdatabase_7

Retrieving read only JDBC Connection for 3
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.database.ox.OXDBService.backR eadOnly(OXDBService.java:107)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.database.schema=oxdatabase_7

Releasing read only JDBC Connection for 3
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.eas.delegate.BaseXMLDelegate. logDebug(BaseXMLDelegate.java:729)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.database.schema=oxdatabase_7
com.openexchange.session.contextId=3
com.openexchange.session.userId=64

3:64:username:EAS:ApplJJ125RRDA4S Client access error
600016: com.openexchange.usm.eas.exception.USMParseRequest Exception: Invalid request content type application/vnd.ms-sync.wbxml, application/vnd.ms-sync.wbxml
at com.openexchange.usm.eas.delegate.BaseXMLDelegate. generateParseException(BaseXMLDelegate.java:521)
at com.openexchange.usm.eas.delegate.BaseXMLDelegate. handleRequest(BaseXMLDelegate.java:111)
at com.openexchange.usm.eas.delegate.BaseDelegate.han dleRequest(BaseDelegate.java:258)
at com.openexchange.usm.eas.servlet.EASServlet.handle Request(EASServlet.java:636)
at com.openexchange.usm.eas.servlet.EASServlet.doPost (EASServlet.java:574)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.openexchange.ajp13.coyote.AjpProcessor.process (AjpProcessor.java:946)
at com.openexchange.ajp13.coyote.sockethandler.Coyote Task.call(CoyoteTask.java:185)
at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.jav a:138)
at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.runTask(CustomThreadPoolExecuto r.java:813)
at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.run(CustomThreadPoolExecutor.ja va:840)
at java.lang.Thread.run(Thread.java:662)
Feb 20, 2014 10:04:49 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.eas.servlet.EASServlet.logRes ponse(EASServlet.java:802)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.database.schema=oxdatabase_7
com.openexchange.session.contextId=3
com.openexchange.session.userId=64

3:64:username:EAS:ApplJJ125RRDA4S: FolderSync executed in 226 ms, no OX calls made.
Feb 20, 2014 10:04:50 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.eas.delegate.BaseXMLDelegate. logDebug(BaseXMLDelegate.java:718)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.session.contextId=3
com.openexchange.session.userId=64

3:64:username:EAS:ApplJJ125RRDA4S Invalid request content type application/vnd.ms-sync.wbxml, application/vnd.ms-sync.wbxml
600016: com.openexchange.usm.eas.exception.USMParseRequest Exception: Invalid request content type application/vnd.ms-sync.wbxml, application/vnd.ms-sync.wbxml
at com.openexchange.usm.eas.delegate.BaseXMLDelegate. generateParseException(BaseXMLDelegate.java:521)
at com.openexchange.usm.eas.delegate.BaseXMLDelegate. handleRequest(BaseXMLDelegate.java:111)
at com.openexchange.usm.eas.delegate.BaseDelegate.han dleRequest(BaseDelegate.java:258)
at com.openexchange.usm.eas.servlet.EASServlet.handle Request(EASServlet.java:636)
at com.openexchange.usm.eas.servlet.EASServlet.doPost (EASServlet.java:574)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at com.openexchange.ajp13.coyote.AjpProcessor.process (AjpProcessor.java:946)
at com.openexchange.ajp13.coyote.sockethandler.Coyote Task.call(CoyoteTask.java:185)
at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.jav a:138)
at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.runTask(CustomThreadPoolExecuto r.java:813)
at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.run(CustomThreadPoolExecutor.ja va:840)
at java.lang.Thread.run(Thread.java:662)
Feb 20, 2014 10:04:50 AM com.openexchange.log.internal.callback.DebugCallba ck log
FINE: Logged at: com.openexchange.usm.eas.servlet.EASServlet.logRes ponse(EASServlet.java:802)
com.openexchange.ajpv13.remoteAddress=127.0.0.1
com.openexchange.session.contextId=3
com.openexchange.session.userId=64

3:64:username:EAS:ApplJJ125RRDA4S: Settings executed in 0 ms, no OX calls made.
Tags: None

Previous template Next

Announcement

Active-Sync: Fehler beim Syncen mit "Invalid request content type"

Active-Sync: Fehler beim Syncen mit "Invalid request content type"