Re: [SOGo] Calendar name changed to non-readable
good, but it's odd that it happened On 08/04/2015 05:01 AM, Khapare Joshi wrote: nope, But i renamed those calendar and it seem to be work -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 08/03/2015 11:26 AM, Christian Mack wrote: Hello Am 31.07.2015 um 18:34 schrieb Anil Thapa: On 07/31/2015 12:08 PM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Thanks, 1. users are from ldap 2. calendars, events are stored in postgresql 3. this is my own account. 4. I do not think this is something to do with authentication because a) this particular calendar is not shared b) if i create new calendar - for example TEST it does create exactly what I write 5. only those two calendar I created long ago had these 147F-4Dcc kind of names. 6. I had already took a look into the logs, when I click on these i see no error, warning message 7. This might be somewhere in the database or the sogo could not translate those to readable format - which I don't know where to fix Khapare Do you use MySQL as backend? Did you set the default language to UTF-8 in the SOGo database? Kind regards, Crhistian Mack Hi No I have been using postgresql since 2010 and SOGo database is set to UTF-8 sogo | sogo | UTF8 | en_US.UTF-8 | en_US.UTF-8 -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 06:05 PM, Steve Ankeny wrote: On 07/31/2015 12:34 PM, Anil Thapa wrote: On 07/31/2015 12:08 PM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Thanks, 1. users are from ldap 2. calendars, events are stored in postgresql 3. this is my own account. 4. I do not think this is something to do with authentication because a) this particular calendar is not shared b) if i create new calendar - for example TEST it does create exactly what I write 5. only those two calendar I created long ago had these 147F-4Dcc kind of names. 6. I had already took a look into the logs, when I click on these i see no error, warning message 7. This might be somewhere in the database or the sogo could not translate those to readable format - which I don't know where to fix Khapare Your conclusions sound logical! Now maybe someone can help you fix it. (1) since it seems not to involve users, looking in LDAP is probably not the solution (2) it sounds like a formatting error (UTF-8 etc.) in the database If I read your e-mail correctly, this started when you recently upgraded SOGo? I'm a little confused about your version number 2.2.16, as I don't remember that version. Can you not upgrade to the latest version, 2.3.1? nope, But i renamed those calendar and it seem to be work Perhaps someone can help (I'm not an expert) It sounds like your database needs a bit of a cleanup. Do you have access to the database from a gui interface or command line? Can you query these calendars? Are these the only calendars effected? Is it possible to rename the calendars (i.e., correct them)? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
Hello Am 31.07.2015 um 18:34 schrieb Anil Thapa: > > > On 07/31/2015 12:08 PM, Steve Ankeny wrote: >> On 07/31/2015 07:36 AM, Khapare Joshi wrote: >>> My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). >>> Something has changed in this version, some reason in my calendar >>> names are not recognizable, instead it prints as : 147F-4Dcc >>> >>> But if I create a new calendar i.e test it is normal. >>> >>> I have attached the screen-shot. anybody has an opinion on this ? >>> >>> K >> >> Are the alpha-numeric-named calendars "shared" calendars from other >> users? >> >> If so, that would seem to indicate the issue has to do with the >> authentication of users -- a scrambling of usernames -- i.e., LDAP, >> SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? >> >> Where is user data stored? It may also simply require a "fresh" >> sharing from the original user. >> >> It might also be helpful to know your OS, etc. >> >> > Thanks, > > 1. users are from ldap > 2. calendars, events are stored in postgresql > 3. this is my own account. > 4. I do not think this is something to do with authentication because > a) this particular calendar is not shared >b) if i create new calendar - for example TEST it does create > exactly what I write > 5. only those two calendar I created long ago had these 147F-4Dcc > kind of names. > 6. I had already took a look into the logs, when I click on these i see > no error, warning message > 7. This might be somewhere in the database or the sogo could not > translate those to readable format - which I don't know where to fix > > Khapare Do you use MySQL as backend? Did you set the default language to UTF-8 in the SOGo database? Kind regards, Crhistian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 12:34 PM, Anil Thapa wrote: On 07/31/2015 12:08 PM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Thanks, 1. users are from ldap 2. calendars, events are stored in postgresql 3. this is my own account. 4. I do not think this is something to do with authentication because a) this particular calendar is not shared b) if i create new calendar - for example TEST it does create exactly what I write 5. only those two calendar I created long ago had these 147F-4Dcc kind of names. 6. I had already took a look into the logs, when I click on these i see no error, warning message 7. This might be somewhere in the database or the sogo could not translate those to readable format - which I don't know where to fix Khapare Your conclusions sound logical! Now maybe someone can help you fix it. (1) since it seems not to involve users, looking in LDAP is probably not the solution (2) it sounds like a formatting error (UTF-8 etc.) in the database If I read your e-mail correctly, this started when you recently upgraded SOGo? I'm a little confused about your version number 2.2.16, as I don't remember that version. Can you not upgrade to the latest version, 2.3.1? Perhaps someone can help (I'm not an expert) It sounds like your database needs a bit of a cleanup. Do you have access to the database from a gui interface or command line? Can you query these calendars? Are these the only calendars effected? Is it possible to rename the calendars (i.e., correct them)? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 12:21 PM, Chris Coleman wrote: Right! My point is, the app should contain informative error messages for every foreseeable error condition, that guide the user to fix their own error most of the time, get help from their sogo mail sys admin some of the time, and finally resort to the mailing list in very rare situations when an unforeseen error occurs and the app doesn't have a built-in informative error message to guide the user to fix it themselves. Without this, basic level 1 help requests flood the mailing list... Sounds like a feature request to me. Write the code to implement it, and I'm sure Inverse will take a look. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 12:08 PM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Thanks, 1. users are from ldap 2. calendars, events are stored in postgresql 3. this is my own account. 4. I do not think this is something to do with authentication because a) this particular calendar is not shared b) if i create new calendar - for example TEST it does create exactly what I write 5. only those two calendar I created long ago had these 147F-4Dcc kind of names. 6. I had already took a look into the logs, when I click on these i see no error, warning message 7. This might be somewhere in the database or the sogo could not translate those to readable format - which I don't know where to fix Khapare -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 7/31/2015 11:38 AM, Steve Ankeny wrote: On 07/31/2015 10:03 AM, Chris Coleman wrote: On 7/31/2015 9:27 AM, Steve Ankeny wrote: On 07/31/2015 09:08 AM, Chris Coleman wrote: On 7/31/2015 8:08 AM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Shouldn't the sogo web user interface display a sensible, detailed error message to the user, if it's indeed encountered a problem when attempting to authenticate/authorize the user's access to some shared calendars. Because displaying 64 digit GUID numbers to the user instead of calendar names, with no explanation, doesn't work. Have you checked the relevant log file? Good idea, but normal users don't have access to global system log files! Users still need to know what when wrong (for example, unable to display certain shared calendars) and why (authorization failure on server xxx with username yyy) and how to fix it by themselves (go to whatever settings page on some menu and try entering correct username/password), or who to contact for help (sogo mail sys admin). That's a different issue than "fixing" the problem. Sorry! I was under the impression the OP wanted to fix his calendars. What you're suggesting may be a feature request but may have little to do with actually fixing the problem. The questions I asked may help. Right! My point is, the app should contain informative error messages for every foreseeable error condition, that guide the user to fix their own error most of the time, get help from their sogo mail sys admin some of the time, and finally resort to the mailing list in very rare situations when an unforeseen error occurs and the app doesn't have a built-in informative error message to guide the user to fix it themselves. Without this, basic level 1 help requests flood the mailing list... -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 10:03 AM, Chris Coleman wrote: On 7/31/2015 9:27 AM, Steve Ankeny wrote: On 07/31/2015 09:08 AM, Chris Coleman wrote: On 7/31/2015 8:08 AM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Shouldn't the sogo web user interface display a sensible, detailed error message to the user, if it's indeed encountered a problem when attempting to authenticate/authorize the user's access to some shared calendars. Because displaying 64 digit GUID numbers to the user instead of calendar names, with no explanation, doesn't work. Have you checked the relevant log file? Good idea, but normal users don't have access to global system log files! Users still need to know what when wrong (for example, unable to display certain shared calendars) and why (authorization failure on server xxx with username yyy) and how to fix it by themselves (go to whatever settings page on some menu and try entering correct username/password), or who to contact for help (sogo mail sys admin). That's a different issue than "fixing" the problem. Sorry! I was under the impression the OP wanted to fix his calendars. What you're suggesting may be a feature request but may have little to do with actually fixing the problem. The questions I asked may help. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 7/31/2015 9:27 AM, Steve Ankeny wrote: On 07/31/2015 09:08 AM, Chris Coleman wrote: On 7/31/2015 8:08 AM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Shouldn't the sogo web user interface display a sensible, detailed error message to the user, if it's indeed encountered a problem when attempting to authenticate/authorize the user's access to some shared calendars. Because displaying 64 digit GUID numbers to the user instead of calendar names, with no explanation, doesn't work. Have you checked the relevant log file? Good idea, but normal users don't have access to global system log files! Users still need to know what when wrong (for example, unable to display certain shared calendars) and why (authorization failure on server xxx with username yyy) and how to fix it by themselves (go to whatever settings page on some menu and try entering correct username/password), or who to contact for help (sogo mail sys admin). -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 09:08 AM, Chris Coleman wrote: On 7/31/2015 8:08 AM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Shouldn't the sogo web user interface display a sensible, detailed error message to the user, if it's indeed encountered a problem when attempting to authenticate/authorize the user's access to some shared calendars. Because displaying 64 digit GUID numbers to the user instead of calendar names, with no explanation, doesn't work. Have you checked the relevant log file? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 7/31/2015 8:08 AM, Steve Ankeny wrote: On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. Shouldn't the sogo web user interface display a sensible, detailed error message to the user, if it's indeed encountered a problem when attempting to authenticate/authorize the user's access to some shared calendars. Because displaying 64 digit GUID numbers to the user instead of calendar names, with no explanation, doesn't work. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Calendar name changed to non-readable
On 07/31/2015 07:36 AM, Khapare Joshi wrote: My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K Are the alpha-numeric-named calendars "shared" calendars from other users? If so, that would seem to indicate the issue has to do with the authentication of users -- a scrambling of usernames -- i.e., LDAP, SQL, Samba-AD, Microsoft-AD, etc. How are you authenticating users? Where is user data stored? It may also simply require a "fresh" sharing from the original user. It might also be helpful to know your OS, etc. -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Calendar name changed to non-readable
My SOGo version is 2.2.16 (root@shiva.inverse 201502121141). Something has changed in this version, some reason in my calendar names are not recognizable, instead it prints as : 147F-4Dcc But if I create a new calendar i.e test it is normal. I have attached the screen-shot. anybody has an opinion on this ? K
