Calendar Migration (read Seventh Level of Hell)

[jeremymaritz]

Hi all,

Is there any other way to migrate calendars from one zimbra server to another than using curl? I've got a few here that are kicking out this error:


The server encountered an
internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>java.lang.NullPointerException
javax.mail.internet.MimeUtility.checkAscii(MimeUti lity.java:1266)
javax.mail.internet.MimeUtility.encodeWord(MimeUti lity.java:595)
javax.mail.internet.MimeUtility.encodeText(MimeUti lity.java:426)
javax.mail.internet.MimeMessage.setSubject(MimeMes sage.java:775)
com.zimbra.cs.mailbox.calendar.CalendarMailSender. createCalendarMessage(CalendarMailSender.java:360)
com.zimbra.cs.mailbox.calendar.CalendarMailSender. createCalendarMessage(CalendarMailSender.java:314)
com.zimbra.cs.mailbox.Mailbox.addInvite(Mailbox.ja va:2980)
com.zimbra.cs.service.formatter.IcsFormatter.saveC allback(IcsFormatter.java:134)
com.zimbra.cs.service.formatter.Formatter$SaveOper ation.callback(Formatter.java:273)
com.zimbra.cs.operation.Operation.schedule(Operati on.java:190)
com.zimbra.cs.service.formatter.Formatter.save(For matter.java:103)
com.zimbra.cs.service.UserServlet.doPost(UserServl et.java:438)
javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:162)
javax.servlet.http.HttpServlet.service(HttpServlet .java:802)

The full stack trace of the root cause is available in the Apache Tomcat/5.5.15 logs.


Digging through the logs doesn't come up with much.

Any thoughts, anyone? I've got some way-around-back ways of doing this (like using the PST Import tool), but I'm aiming for best practices here.

Thanks!

[jhahm]

Hi, it looks like you're hitting this bug:

Bug 13781 - NPE while subscribing to a remote Japanese ics

This is fixed in ZCS 4.5.1. What version are you on?

Look at your ics file and see if there are any VEVENTs that have empty SUMMARY value or are missing it. Set SUMMARY to something to workaround the bug.

[jeremymaritz]

We were on 4.5.0, but upgraded to 4.5.6 last night.

It appears that the SUMMARY=EMPTY is a problem with some of the entries. Fixing it enabled the import to succeed.

We've also noticed that every instance of ATTENDEE;CN needs to be replaced with ATTENDEE;RSVP=FALSE, as these are entries where the user hasn't RSVP'd to an appointment yet, and Zimbra doesn't seem to like these on the import without specifying the RSVP status.

Not sure if that's a bug that was noticed and fixed already, though.

Cheers!