Re: Invalid byte sequence when accepting event

Michael J Rubinsky <[email protected]> Thu, 27 Jul 2017 13:28:57 +0000
Newsgroups gmane.comp.horde.kronolith
Message-ID <20170727132857.Horde.LX3TYc6r0FHfXbtw_W1CPE5@h4.theupstairsroom.com>
Quoting [email protected]:

> Zitat von Michael J Rubinsky <[email protected]>:
>
>> Quoting [email protected]:
>>
>>> Zitat von Jan Schneider <[email protected]>:
>>>
>>>> Zitat von [email protected]:
>>>>
>>>>> Hello,
>>>>>
>>>>> today we got the following error when trying to accept a invite  
>>>>> from one Horde user to another :
>>>>>
>>>>> Jul 26 16:31:47 webmail HORDE: [kronolith] SQL QUERY FAILED:  
>>>>> SQLSTATE[22021]: Character not in repertoire: 7 ERROR:  invalid  
>>>>> byte sequence fo                                                  
>>>>>                                                r encoding  
>>>>> "UTF8": 0xf6 0x72 0x67 0x20
>>>>>     INSERT INTO kronolith_events (event_id, event_uid, event_creator_id,
>>>>>       event_title, event_description, event_location, event_timezone,
>>>>>       event_url, event_private, event_status, event_attendees,
>>>>>       event_resources, event_modified, event_start, event_end,  
>>>>> event_allday,
>>>>>       event_alarm, event_alarm_methods, event_recurtype,  
>>>>> calendar_id) VALUES
>>>>>       ('m3S_DfjWK-KhdFuqJQHNyCH',
>>>>>        
>>>>> '040000008200E00074C5B7101A82E00800000000170A59505D5FCE41AA27C7A904474
>>>>>       D1B100000009378262B6DF6AC4ABEF0A516E6103476', 'xxxx',
>>>>>       'Führungsrunde', '', '', NULL, '', 0, 2,
>>>>>        
>>>>> 'a:3:{s:16:"[email protected]";a:3:{s:10:"attendance";i:1;s:8:"response
>>>>>       ";i:1;s:4:"name";s:16:"[email protected]";}s:21:"[email protected]"
>>>>>        
>>>>> ;a:3:{s:10:"attendance";i:1;s:8:"response";i:1;s:4:"name";s:16:"J▒rg
>>>>>       xxxx";}s:17:"[email protected]";a:3:{s:10:"attendance";i:1;s:8:
>>>>>       "response";i:1;s:4:"name";s:14:"xxxx xxxx";}}', 'a:0:{}',
>>>>>       1501079507, '2017-11-23 08:00:00', '2017-11-23 16:00:00',  
>>>>> 0, 15, 'N;',
>>>>>       0, 'xxxx') [pid 32203 on line 236 of  
>>>>> "/usr/share/php/Horde/Db/Adapter/Pdo/Base.php"]
>>>>>
>>>>>
>>>>> For sure it looks like the display name is not properly encoded,  
>>>>> but can soemone explain how to avoid this Problem. All the  
>>>>> Horde/Kronolith are at latest versions and the database used ist  
>>>>> PostgreSQL. Browser used from the failing Client is Chrome on  
>>>>> Windows OS.
>>>>>
>>>>> Thanks for any hints
>>>>>
>>>>> Andreas
>>>>
>>>> We would probably have to normalize any external data to UTF-8  
>>>> before storing to the backend.
>>>
>>> Hm, yes. Further investigation showed that the invite was created  
>>> by Windows 10 Mail App tied with ActiveSync to the horde  
>>> installation. It looks like the display name of the attendee is  
>>> not properly encoded. I can send the raw E-Mail invite to some  
>>> developer if this would help?
>>
>>
>> Can you please create a ticket on bugs.horde.org as well? I will  
>> look at this.
>>
>
> A Ticket for Kronolith or ActiveSync or Horde? Do you need some  
> example invite?

In the Synchronization queue would be great, but I can move it where  
ever you place it. A sample invite would also be helpful.

>
> Thanks
>
> Andreas
>
>
> -- 
> kronolith mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: [email protected]



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
(unnamed) (application/pgp-keys, 9.1 KB) - not displayed
signature.asc (application/pgp-signature, 821 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4

iQIcBAABAgAGBQJZeeqZAAoJEJGSgkbRsxbbYVUQAKXXf7ZdcCIsDJDg/E8U550O
wrVUoCb3qxXRaqHuVlOBDDjm9zMzYqtVgoafTdjXMGIyA5WgO8PsgRefDYfrJdEA
9Cy/wKtoSFoVJ6EBRwg5EfU+O2s7nRoc6oljelnxnbz8ssJ+TbF3Tnw9HL9HYjCy
k9K0+eJL83RomtQYBftAkFOtySEDVbrfRbDllZHTyL35XA2rYv3MSaheMO4j9RLB
QJ7f4CzOivSQdzh3sn0h/Kd4NAJZYL0zDletMhKdCmxEMm+g0fqocaB+ciYCbPLW
DKqG1M7it3HWyerdjQjOdfced4umIsffyMt9sFGChz4eYXXwb8RUp3IMFlKJeDty
fWiVy7XREPWLBrI6D3TboTVSzOX0S7LMT/aU57jO9oUTWsw0UH3TgwTDnS004iwB
ValxoPUYP3QboagcMoj2QHiVoBisU3gmkCHhDse3z3mwaMSbG+Es8jb7ardSCzYA
WkNizF2YoN4BoL4YUyTGZqbwDdlCyEnmOSQHgMlexhsTCOsBP6N6zWpFYSo4bVwt
nbit7bDfL5dwO0BdCZVhQ9Zi+AxBAeu7qh0PJF9YS01ooRPCriK7BMh22QvlqsAy
YY39xywpgB00I5vos8UFVDKUHQFB3dbRVSITvYIl68Tt8wW7wfSaWpHdhS7Qpk84
NUCgOOAYeEdsXLEME5zw
=RPZC
-----END PGP SIGNATURE-----