Appointment charset (encoding?) problem on ZCS 6.0

[Andrew Orlov]

Hello, all!

We met some serious trouble on our new ZCS 6.0: our localized appointments (ru_RU) are shown as sets of question signs (like "????? ?????...") after server restart. All newly created appointments are shown correctly - we can login/logout to our accounts, everything is fine until restart.

It is reproduced, so it can be bug... See steps to repeat below.

1. We installed clean ZCS 6.0 on Linux (tested on SLES10SP2 x32, x64 and Debian5 x64).

2. Let's login to ZCS, go to Calendar tab and create new appointment:


3. Save appointment. We can see the following nice picture:


4. Restart Zimbra server. Our appointment is now corrupted:


5. What is inside of it? Let's see. Theme and Description are OK, but Location is corrupted too:


6. Let's return to the Calendar view and make Search by all the calendar items (type "*" in search input field and push Search button). We can see some kind of miracle - our appointment is now correct again!


If we open it we'll see all the field displayed correctly (even Location)...

8. Let's now refresh Calendar tab using Refresh button near New button. Picture is now bad again as shown in 4...

May be, somebody met and won such problem??? Any help will be very appreciated!

We found workaround, but it's not a real solution... Analyzing HTTP requests/responses I found that all the calendar items were returned correctly using any kind of search (like search for all items, "*" wildcard). So, I slightly modified CalendarCore_all.js and Startup2_all.js on server (and gzipped them back, of course).

Both the js-files have function _setSoapParams, where defaults for calendar search are set. I changed

query = (query != null)
? (query + " (" + params.queryHint + ")")
: params.queryHint;

to

query = (query != null)
? (query + " (" + params.queryHint + ")")
: ("* (" + params.queryHint + ")");

emulating "all-items search". Now it works perfectly, but really it is not a solution, only workaround...

I suppose the reason of the problem is in Zimbra java code with some incorrect charset conversion for default calendar search without parameters...

Developers or anybody, help!...

[Andrew Orlov]

Bug is confirmed.

Bug 41017 – Charset problem in localized appointments (ZCS6.0)

Looking forward patch... Dear developers, if I can help, feel free to ask me. Now we forced to suspend our migration from MSExchange .

[Mistoffeles]

You could always use Zimbra 5 until the bug is fixed, then upgrade.

Personally I never use something brand new, whether it's a MS OS, a Linux distro (Except RHEL, and even then I am cautious), or application software, on a production server. (Of course, I experiment with stuff that isn't business critical, like iPod jb-ing and *cough* penetration testing *cough*).

Cheers.

[Andrew Orlov]

Bug is fixed! Dear developers, thanks a lot!!!

Mistoffeles, in general you are right, but our migration was sheduled a long time ago and now we just MUST begin it. It is reputation question... We had some issues in Zimbra 5 so looked forward ZCS6.

[Mistoffeles]

I'm glad the bug that was stopping you is now fixed.

I am curious, though, why you would schedule a rollout "a long time ago" of a product that had not been released yet.