Announcement

Collapse
No announcement yet.

Sync on Samsung i9000 Galaxy S (android)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sync on Samsung i9000 Galaxy S (android)

    Hello,

    we have a few new GalaxyS Android-Smartphones (Android 2.1) , which we want to sync to our OX Accounts.
    Some Accounts are functioning perfectly, others don't. I also made a completely new account, but this is also not syncing. We already changed the smartphones, but this is not the problem.
    This is a corresonding error-Message I found in the open-xchange.log:

    Jul 16, 2010 12:00:33 PM com.openexchange.usm.eas.delegate.BaseXMLDelegate logError
    SEVERE: 3:14:info@xxxxx.de:EAS:droid1279201122612 OX server returned error
    400015: com.openexchange.usm.api.exceptions.OXCommunicatio nException: OX server returned error, json-error={"code":"CON-0209","error_id":"-645386201-195919","category":3,"error_params":[6,3,14],"error":"You do not have permission to create objects in this folder %1$d in context %2$d with user %3$d"}
    at com.openexchange.usm.contenttypes.util.AbstractTra nsferHandler.checkResult(AbstractTransferHandler.j ava:393)
    at com.openexchange.usm.contenttypes.util.AbstractTra nsferHandler.getListOfResults(AbstractTransferHand ler.java:283)
    at com.openexchange.usm.contenttypes.util.AbstractTra nsferHandler.readStandardFolderContent(AbstractTra nsferHandler.java:469)
    at com.openexchange.usm.contenttypes.util.AbstractTra nsferHandler.readStandardFolderContent(AbstractTra nsferHandler.java:444)
    at com.openexchange.usm.contenttypes.util.AbstractTra nsferHandler.readStandardFolderContent(AbstractTra nsferHandler.java:439)
    at com.openexchange.usm.contenttypes.util.AbstractTra nsferHandler.readFolderContent(AbstractTransferHan dler.java:428)
    at com.openexchange.usm.eas.delegate.SyncDelegate.cre ateUserIdNameEmailMap(SyncDelegate.java:272)
    at com.openexchange.usm.eas.delegate.SyncDelegate.get UserIdMap(SyncDelegate.java:1357)
    at com.openexchange.usm.eas.delegate.sync.OrganizerOp erationXmlType.writeXml(OrganizerOperationXmlType. java:77)
    at com.openexchange.usm.eas.delegate.sync.OrganizerOp erationXmlType.writeToXML(OrganizerOperationXmlTyp e.java:71)
    at com.openexchange.usm.eas.delegate.SyncDelegate.wri teApplData(SyncDelegate.java:544)
    at com.openexchange.usm.eas.delegate.SyncDelegate.wri teAddElement(SyncDelegate.java:1230)
    at com.openexchange.usm.eas.delegate.SyncDelegate.wri teCommandsInResponse(SyncDelegate.java:1101)
    at com.openexchange.usm.eas.delegate.SyncDelegate.wri teCollectionInResponse(SyncDelegate.java:1015)
    at com.openexchange.usm.eas.delegate.SyncDelegate.han dleRequest(SyncDelegate.java:245)
    at com.openexchange.usm.eas.delegate.BaseXMLDelegate. handleRequest(BaseXMLDelegate.java:96)
    at com.openexchange.usm.eas.servlet.EASServlet.handle Request(EASServlet.java:468)
    at com.openexchange.usm.eas.servlet.EASServlet.doPost (EASServlet.java:350)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:616)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:689)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.doServletService(AJPv13RequestHandlerImpl.java: 504)
    at com.openexchange.ajp13.AJPv13Request.response(AJPv 13Request.java:129)
    at com.openexchange.ajp13.najp.AJPv13RequestHandlerIm pl.createResponse(AJPv13RequestHandlerImpl.java:31 6)
    at com.openexchange.ajp13.najp.AJPv13ConnectionImpl.c reateResponse(AJPv13ConnectionImpl.java:207)
    at com.openexchange.ajp13.najp.AJPv13Task.call(AJPv13 Task.java:346)
    at java.util.concurrent.FutureTask$Sync.innerRun(Futu reTask.java:269)
    at java.util.concurrent.FutureTask.run(FutureTask.jav a:123)
    at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.runTask(CustomThreadPoolExecuto r.java:737)
    at com.openexchange.threadpool.internal.CustomThreadP oolExecutor$Worker.run(CustomThreadPoolExecutor.ja va:763)
    at java.lang.Thread.run(Thread.java:595)

  • #2
    Hi,

    it seems like the device tries to create entries at the global address book. Can this be disabled at the device? You could enable EAS debug logging at eas.properties and provide the corresponding call.

    Greetings
    Last edited by Martin Heiland; 07-16-2010, 03:20 PM.

    Comment


    • #3
      Hello Franz Pfisterer, der Sync auf meinem Samsung Galaxy S funktioniert auch nicht 100%ig, ich habe u. a. das "All Day" Problem. Wenn ich auf dem I9000 Smartphone einen Termin eintrage mit "all Day", dann macht ein Sync mit OX daraus einen 2 tägigen Eintrag. Habe verschiedenste Zeiteinstellungen mit GMT ausprobiert, Problem bleibt. Habe das Problem mit dem originären I9000-eXCHANGE-account ALS AUCH MIT ROADSYNC ALS AUCH MIT TOUCHDOWN.
      Haben Sie mittlerweile Ihre Sync-Probleme gelöst ???

      Danke
      BK

      Comment


      • #4
        Das Problem besteht seit dem letzten großen Update vom OX-Server nicht mehr.

        Comment

        Working...
        X