EWS resource fails to retrieve folder tree #2
Comments
|
Same problem here. I tried it with 3 computers (Gentoo at home desktop and laptop, Arch Linux at office). The target is an Exchange 2013 server. I can see the folders in the subscription tab, and the entry in Akonadi is also showing the green dot. But I cannot see any account in Kmail, calendar or addressbook. Also the browser in Akonadi-Console isn't showing any entry for the Exchange account. But I can see an akonadi_ews_resource process running. |
|
As mentioned on KDE bug moving discussion here. As of this morning kontact crashes (may be totally unrelated?). Note that I've installed the akonadi-ews-dbg_0.8.0-1_amd64.deb package as otherwise backtrace showed nothing. While posting the other comment below related to the crash specific to akonadi_ews_resource I also noticed a kontact*.crash file. Now attached. gdbCommands.txt |
|
BTW, just noticed that starting kmail in standalone mode (instead of kontact) does not segfault. Although the folder issue remains.. Here is the shell output for kmail: This message may be interesting: While trying to find that I noticed the following file: |
|
I'm going to check that crash to see where it failed. In the meantime can you try this for me:
and:
You can send me the whole log if you want, but before doing that make sure there is nothing confidential in it. |
|
ok, manage to come-up with something that hopefully will make some sense to you. For others, I used the following:
|
|
Strange. I don't see any messages that should be activated by the |
|
I'm not much used to And it also pointed to temporary files located in Clearly it did not cleaned-up it's temporary files afterwards ;) |
Smells like your Exchange server has had enough ;) You can try to add I am never actually sure what is the correct syntax in different shells. |
|
Using |
|
That Internal Server Error is strange - the request that was sent seems perfectly in order. Let's take out a larger cannon... Can you create (or edit if exists) the file
This will dump some XML into the log and create more files in |
|
I got your logs with the full request dumps. It looks like for some reason it can easily retrieve the list of folders using a FindFolder request (for the subscription window), but trying the same using SyncFolderHierarchy (for the main folder tree) fails with an internal server error. I'll dig into the documentation to see if there are any gotchas. BTW, you have a lot of folders (>400) - this might be an important factor here. |
|
Well, long-term enterprise level usage usually mean larger scale sizes :) |
|
The fun part is that it's probably a Microsoft bug, that I'll end up working around. You see, some requests that handle large amounts of data (like retrieving the list of e-mails from a folder) are prepared for pagination. You specify that you want to receive say the first 100 items and you'll get up to a 100 with a flag telling you if there's more. If yes, you fetch another 100 and so on. The SyncFolderHierarchy request, which was added exactly to synchronize folder trees lacks this feature (the sibling request for folder items - SyncFolderItems - does have it). It would be nice to find out at the server side what the details of the ISE error are, but I guess that would require a word with the admins, who are not always happy. I'll keep digging/working around. |
|
like above i have now the same issue. here is my kmail output: ` |
|
I had the same issue. I gave a try to the workaround on the 'syncfolderhierarchy-workaround' branch and it worked for me. Thanks! |
|
Thanks for Your work! At last 'syncfolderhierarchy-workaround' branch is working on Manjaro linux. Contacts and calendar also working. |
|
I'm having this exact problem seemingly. I'm not compiled from source, though. Maybe I'm crazy 👍 but can release a 0.8.1? |
|
Yes, it will be nice with syncfolderhierarchy-workaround branch. Stable enough. |
|
Thanks for letting me know. I was working on more improvements in that area as during investigations I have found some more minor issues. The code is almost there, but unfortunately for the last weeks I don't have much spare time to work on this so please bare with me. My original intention was for the next release to include a more feature-complete calendar but I'm leaning towards doing a bugfix release once I close most of the issues found in the initial version, so please stay tuned. |
|
This was fixed for me after putting https://github.com/KrissN/akonadi-ews/compare/syncfolderhierarchy-workaround.patch into /etc/portage/patches/kde-misc/akonadi-ews-0.8.0. I hope you can release a bugfix release soon. Thanks for this great piece of work. |
|
Do you have instructions for building from source (n00b at KDE packaging) or can we get an updated build package to try out? |
|
@cardonator For Gentoo it's as easy as putting the patch in /etc/portage/patches/kde-misc/akonadi-ews-0.8.0: |
|
I have just committed a revised folder tree synchronisation logic to |
|
I've downloaded the following patch and put it in portage's patch directory as outlined above (and removed the other): It compiled fine but so far I'm having timeout problems connecting to EWS (OWA also doesn't work). I'll report back as soon as it works again. |
|
In the journal, I'm seeing the following messages repeated a few times per minute: What does it tell me? |
|
This tells me, that my latest incremental folder tree sync changes need some more love... However the full sync that happens afterwards should still work. Do you see the folder tree? |
|
Yes, in KMail I see the folder tree and all current mails. However, in Akonadi Console, I see the folder tree but no items. Strange but I think this is unrelated: It doesn't work for any folder there. If you need more logging, tell me how I can provide it. I'm connecting to EWS 2013. |
|
It shows something like this with these debug settings: https://gist.github.com/kakra/5c831d1a6fb0c009ac375c77dcb25a6f |
|
@kakra actually I have just now read your comment once again and noticed that you're reporting that you can see e-mail in KMail, but no items in Akonadi Console. This seems to be a problem in Akonadi Console itself (my guess is that it hasn't been implemented). I can't see any items in it either. The log you have posted is correct. I can see the Internal Server Error at the first attempt to retrieve the folder tree followed by a fallback to the backup method, which succeeded. If you can see the folder tree now then this means the latest code works fine now and I can finally close the issue. |
|
@kakra Is there any way to do something similar in Kubuntu? I'm afraid I've never compiled a KDE plugin like this before so I'm not sure how to compile the latest source. |
|
@cardonator If you have a src-deb package, it should be pretty straight forward. Install the source package (you'll find it in /usr/src) and build-essentials. Then add the patch to the package build instructions and let the packaging tools build a new deb package which you can then install with dpkg. Apparently, I cannot give you more detailed instructions here as I usually admin Gentoo systems only. Just very rarely I'm using Ubuntu systems and need to integrate patches there. But it is not that difficult and there are good instruction online that you can find. If you already installed akonadi ews as a deb package, I'm sure you'll find a deb-src package at the same location that you can build upon. |
|
That makes sense. Unfortunately, I am using the compiled release from this repo and it doesn't appear that there is a src package for deb. |
|
@cardonator Did you add the corresponding deb-src line to the apt sources before trying to install the src package? Usually you just duplicate the deb line and put deb-src in front (replacing deb). |
|
The package here is just installable. It's not in a PPA/package repo. Can you add a git repo as a package source or something? |
|
@cardonator If it is in the original apt sources, then enable the corresponding deb-src line in /etc/apt/sources.list or sources.list.d/*. Then run "apt-get update", and then "apt-get {build-dep,source} packagename". You'll find the source in /usr/src then. You can place the patch there, update the build rules/manifest, then rebuild a deb package which you can install with dpkg. Here's a few pointers in the right direction: http://askubuntu.com/questions/246690/how-to-use-apt-to-get-source-code-and-then-do-separate-compile |
Imported from KDE bug 78629.
Vincent Fortier says:
In this case I manually entered the EWS URL and hit Try connect. Which i found simpler to evolution as the user don't really care about the underlying UUID type OAB URL. Although a connection successful may be appropriate? It ended up not adding any folder within kmail for the new account (maybie a bug related to kmail and totally unrelated to your new feature, will further investigate?). Although from the subscription tab I can select my various folders and as well, it says "ready" under it in the reception tab.
The text was updated successfully, but these errors were encountered: