Note that for tracebacks and other large amounts of output, we have a pastebin that you can then refer to in tickets with P4 for example.
Thanks for the tip. I'll do that when I get a free cycle. I'm very interested in getting all this working, so I'll prioritize it right under two other high tasks I have (as well as my regular paying job).
@Kimmo What you have installed as part of Kolab are web applications just like you would have them installed if it were without Kolab. There's no Kolab-specific extras or conditions for as far as the principle category of "a web server serving a web application written in PHP" goes.
I had the same problem and I'm very happy that I'm not the only one.
I just updated the whole system - there were plenty of kolab updates - and rebooted afterwards.
The error was still there.
So people still need to drop that table .. ( I thought maybe the update will fix it automatically)
Kolab use Apache by default. Try to map apache to another port ( for example 8080) and test kolab admin app with this port. If it works you could try use nginx as front-end or main web server for kolab. I mean that it requires step-by-step solution and finding problems. Because kolab imho is very moody.