[SOLVED] Delete Single or Recurring Calendar Entry Error?

[Chewie71]

I have a user who created an appointment and did something wrong when setting the end date. The appointment recurs forever (daily) with the existing date being the start date and the end date being 4 months out...maybe longer.

So he has all these multiple month length appointments that start every day until the end of time...or the end of what the calendar knows anyway.

When he tries to delete these through the GUI he gets an error. I watched the log as he did this and got the following error message...

2007-08-27 11:55:21,179 INFO  [http-443-Processor55] [name=username@domain.edu;aname=admin@domain.edu;mid=310;ip=xxx.xxx.192.36;ua=ZimbraWebClient - FF2.0 (Win)/4.5.6_GA_1023.RHEL4_64;] CancelCalendarItem - <CancelCalendarItem id=130e28ce-bebc-48fd-81b4-bc35ec674272:1077-1086 comp=0>
2007-08-27 11:55:21,235 INFO  [http-443-Processor55] [name=username@domain.edu;aname=admin@domain.edu;mid=310;ip=xxx.xxx.192.36;ua=ZimbraWebClient - FF2.0 (Win)/4.5.6_GA_1023.RHEL4_64;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: metadata too long
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:175)

So the metadata is too long...well duh.... Is there anyway I can remove these events from his calendar from the CLI? I tried using zmmailbox deleteItem using the item ID# that is in that logged error but that is not seeming to work.

zmmailbox selectMailbox username@domain.edu deleteItem 130e28ce-bebc-48fd-81b4-bc35ec674272

Any other ideas?

Thanks,
Matt

[jholder]

hi Chewie-
Sorry you're having difficulty.

This is a bug, and we'll be fixing it in 4.5.7.

The only other thing we can do as a workaround is find the appointment entries that are causing the problems, delete them from the database, and recreate them. That should sort out the metadata information. The tricky part is finding all the entries that are doing it.

There's a fair amount of poking around in the MySql db and the raw mail store required, so you might just want to wait until 4.5.7

Cheers,
john

[Chewie71]

OK...we'll wait.

The problem doesn't start appearing in his calendar until sometime in October. We'll get by for now.

Thanks,
Matt