Menu

Office365 (Exchange 2013) KDE Kontact : ErrorInvalidIdMalformed Id is malformed

Help
skipperTux
2014-08-28
2014-09-13
  • skipperTux

    skipperTux - 2014-08-28

    Hi,

    when connecting to our Office365 calendar using Kontact - KOrganizer 4.14 I get the message "ErrorInvalidIdMalformed Id is malformed". This happens when either using the URL

    https://outlook.office365.com/ews/exchange.asmx
    

    or

    https://outlook.office365.com/owa/
    

    with the Exchange Protocol set to EWS or Auto. However when using the first URL and login with my credentials, I get the MS service page with the EWS wsdl definition. I can also sign in with my credentials using web access.

    The configuration of the Akonadi DAV groupware resource looks fine. My remote URL has the schema

    http://localhost:1080/users/first.last@domain.com/calendar/
    

    using my credentials as username and password. Also fetching the discovered collections for CalDAV returns the Calendar.

    My system is Arch Linux with the latest updates, OpenJDK 1.7.0_65, DavMail 4.5.1-2303 and KDE - Kontact 4.14, following the logs and my (current) config.
    Any ideas or help is appreciated.

    christoph

    Update 2014-08-28
    Moved logs to attachments.

    Update 2014-09-13
    Fixed KMail -> KOrganizer

     

    Last edit: skipperTux 2014-09-13
  • skipperTux

    skipperTux - 2014-09-13

    More research: I found out read access to an Office365 calendar works fine without errors, events created using the Office365 web-access show up in Kontact - KOrganizer. After adding a new calendar item (e.g. event) in KOrganizer (locally), synchronization fails with error

    There was a problem with the request. The item has not been created
    on the server. An unexpected error (401) occurred while attempting
    to upload
    http://localhost:1080/users/user@domain.com/calendar/bb102bd3-5051-4451-bf08-5f3534a47b46.ics. (401).

    and HTTP/1.1 401 Unauthorized in the DavMail log, or Id is malformed if the .ics-item was imported.

    I would have expected commit 2078 fixes this, but in my case it does not. However obviously nobody else is having this issue with Office365; it also might be a Kontact - KOrganizer problem?

     

Log in to post a comment.