Is it possible this happens when you daily SQL backup is running?

If you are using mysql, make sure to use the

–single-transaction

it will not slow down the availability of the database.

I combine with --single-transaction --routines

If you never used --single-transaction before, this problem would grow over time, as your DB gets bigger.

Two ways your can get client devices asking for password again:

The Z-Push is available, but kopano-server is not available

If the database server is too slow to accept new requests (or not available/offline), kopano-server can’t do much in regards to authenticating users.

https://documentation.kopano.io/kopanocore_administrator_manual/backup_restore.html

Marc

Took me some time to figure this out, so if someone else stumbles upon the problem:

setdefaultsignature.py is no longer available on github, it was removed with this commit

the replacement for this is kopano-webapp-admin.py which is available here and worked fine for me when run with pyhon3.

Other problems I’ve just stumbled upon:

Kopano-WebApp/DeskApp doesn’t offer calibri font, so if half your company uses Outlook and half uses Kopano DeskApp, you can’t have those DeskApp users write in the same html font (which was set as corporate standard by the outlook users).

Kopano-WebApp/DeskApp doesn’t allow embedding images, for which there is a workaround (previously setdefaultsignature.py, but this does not seem to exist anymore, now there is kopano-webapop_admin.py which should be used along with a manually created signature in a text editor with the image embedded as base64 code). This does actually work, and making it work and having the image properly embedded for two users only took me two hours.

@bob4os Ahh nevermind… The nextcloud 22 upgrade killed the birthday calendar. I had to recreate it by enabling and disabling it.
Now i see other strange things, can you check if you have something like this aswell? (seems like you are also sporting nextcloud and z-push.)

Nextcloud
9a37bc39-e43f-4a77-8d73-b551ca71e304-image.png
Outlook
c35f71df-ab3c-4d64-ae40-1127f51306d5-image.png

@bioprojekt-gmbh
Hi,
our customers and employees also complain about this problem. Unfortunately it cannot be solved yet.
Thanks, Siegfried

I’m using the combined backend with caldav, carddav, imap, stickynotes and searchldap for GAL.
Yes, PHP 8 will be mandatory in a year.

@dbuggmbh said in Complete removal of DeskAPP on windows:

Unfortunately the complete removal and new installation of the deskapp did not solve the problem.

The DeskApp still hangs with a black window on some emails, while the webapp has no issues whatsoever on the same system.

Any ideas on what to do to resolve this?

I had this problem some month ago. It was a driver problem with nvidia cards and driver problems with hardware acceleration.

Search for chrome bleck Windows to solve this problem.

It is not the DeskApp, Deskapp is a version of chromium… so the error was in the driver…

@businesstux
i know this is an old thread but im currently trying to include the “only add attachment from mail element”-function but im a bit stuck.

can you share your snippet where and how i need to extend this function?

best regards,
coffee_is_life

@chris_60 I don’t think robing will answer our question, the account is inactive (“former employee”)

@flobian
The solution was a complete reboot of my CentOS7 machine
I dont know what happend or why, but since the reboot the error was gone.

Further i dont know if your error is comparable to what is mentioned above.
whats the exact error your kopano-search.log?

best regards,
coffee_is_life

@flobian
well I updated now too. We are running the same UCS version now. No luck at all.

Still this message after logging in to UCS and try to use kopano meet. Still unsure whether this message is triggered by not being able to connect to the ucs-kopano turn server, or not.

failed_conn_kopano.JPG

Outlook ignores the followup flag with ActiveSync accounts as far as I know.
I had to install the Kopano Extension.

@junglemarc +1

@gerald Got them! Thanks a lot!

I’ll try to avoid them but for some “hardcore” users i suppose I’ll have no choice (keeping them @ Office/Outlook 2013 should not be a problem)

Thanks again!

Regards