> > >From a terminal do > > > > EWS_DEBUG=2 evolution > > > > I don't know why the EWS debugging things were omitted from > > > > https://wiki.gnome.org/Apps/Evolution/Debugging > > > > Thank you. I piped the information into a file ( &> ). I am however not > sure what to look after.
Basically any errors, permission denied, timeouts that sort of thing. > The zombies are still created. Evolution does > no longer crash, but the calendar is only incompletely synchronized. > Only events that I have entered today (from a different client) show up. > Manual refresh has no effect. Try creating a new Linux account, then from that account create the EWS account in Evolution. This will start you with a new clean configuration and see if that then works correctly. If it does, then you will know it's something to do with the configuration and not the server or the install of Evolution. > > > > > EWS does work on Evo 3.10.3, it may be that there is something odd > > with > > the specific configuration you are using (either at your end or the > > Exchange end). It may just be that you need to clean the cache/index > > files - but I don't know enough about EWS and calendars to know if > > that > > could be an issue. > > It would be great to get a hint on how to clean the cache. I cannot > influence the Exchange end. The cache is stored in ~/.cache/evolution/calendars - you could try shutting down Evolution (and all the backend processes), and rename that folder - Evolution should recreate it all when you restart. P. _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
