View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004641SOGoBackend Calendarpublic2019-01-14 16:082019-02-19 18:22
Reporterrobers@tutech.de Assigned To 
PriorityhighSeveritymajorReproducibilityunable to reproduce
Status newResolutionopen 
Platform[Server] LinuxOSRHEL/CentOSOS Version7
Product Version4.0.5 
Summary0004641: Error during sync between Outlook 2016/CalDavSynchronizer 3.40 and SOGo 4.05
Description

Hello there,

as said above, we have a CentOS7 Server, SOGo 4.05 with MySQL 5.7.24 Backend
and Outlook2016/CalDavSynchronizer 3.40 as client. Suddendly there are
synchronisation errors with the error message in SOGo log:

"ERROR(-[GCSFolder writeContent:fromComponent:container:toName:baseVersion:])
Data too long for column 'c_uid'"

and the appointments don't get synchronized from Outlook 2016 to SOGo.
This happened suddenly without changing anything within the configuration
or adding/removing appointments in Outlook or SOGo Webclient.

Is there anything I could do, to get more information what triggers this
error or rather get rid of this error and get OL/SOGo get synchronized again?
At the moment I have no idea, what happened or what to change to get a functional
synchrnoization again. So any help is very appreciated.

Many Thanks!
Thomas

Steps To Reproduce

Sorry I can't reproduce this with another account and at the moment there's only one account which has this problem, but get this error solved would be very nice.

TagsNo tags attached.

Activities

robers@tutech.de

robers@tutech.de

2019-01-15 09:51

reporter   ~0013259

I found a solution for the problem, but I don't know if there are
any side effects that cause other errors. The solution I found is:

The "c_uid" column in the table " sogoroberstu00201dc1fda_quick"
was of the type varchar(255) and the generated uid from Outlook
had more than 255 characters namely 541. So I changed the type
from varchar(255) to varchar(1000) and now Outlook/CalDavSynchronizer
and SOGo are synchronized without errors again.

The one question left is: Does changing the type of the column from
varchar(255) to varchar(1000) has any known side effects? Or is it
secure the change it, because I can't change the way Outlook creates
the uids, right?

Any further information is appreciated.
Many thanks.
ludovic

ludovic

2019-02-19 18:22

administrator   ~0013389

There shouldn't be any side effects. You should also change the c_uid one too.

Issue History

Date Modified Username Field Change
2019-01-14 16:08 robers@tutech.de New Issue
2019-01-15 09:51 robers@tutech.de Note Added: 0013259
2019-02-19 18:22 ludovic Note Added: 0013389