Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Users
Reload this Page Zimbra Desktop - Updated several calendar entries, now I receive these messages

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-03-2008, 08:20 AM
Loyal Member
  
Posts: 91
Default Zimbra Desktop - Updated several calendar entries, now I receive these messages
I'm constantly receiving these errors as new e-mails since I updated several calendar entries in my Zimbra Desktop. I don't know which entry is causing the problem. I reviewed all the entries I updated / added and they all have times. Is is possible for me to find out which entry is causing the problem?

I've attached the error message below.

Product name: Zimbra Desktop
Product version: 0.90
Build ID: 1278
Release type: BETA
OS Platform: Windows XP x86 5.1
Time of event: 2008-10-03 10:12:33
Error type: service.INVALID_REQUEST
Error summary: push item failed

Failure details:
----------------------------------------------------------------------------

<soap:Fault>
<soap:Code>
<soap:Value>soap:Sender</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text>invalid request: Request must have allDay="1" if using a DATE start time instead of DATETIME</soap:Text>
</soap:Reason>
<soapetail>
<Error xmlns="urn:zimbra">
<Code>service.INVALID_REQUEST</Code>
<Trace>com.zimbra.common.service.ServiceExceptio n: invalid request: Request must have allDay="1" if using a DATE start time instead of DATETIME
Code:service.INVALID_REQUEST
at com.zimbra.common.service.ServiceException.INVALID _REQUEST(ServiceException.java:190)
at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teElementCommon(CalendarUtils.java:758)
at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teForCancel(CalendarUtils.java:259)
at com.zimbra.cs.service.mail.SetCalendarItem$SetCale ndarItemInviteParser.parseInviteElement(SetCalenda rItem.java:72)
at com.zimbra.cs.service.mail.ParseMimeMessage$Invite Parser.parse(ParseMimeMessage.java:129)
at com.zimbra.cs.service.mail.SetCalendarItem.getSetC alendarItemData(SetCalendarItem.java:150)
at com.zimbra.cs.service.mail.SetCalendarItem.parseSe tAppointmentRequest(SetCalendarItem.java:216)
at com.zimbra.cs.service.mail.SetCalendarItem.handle( SetCalendarItem.java:97)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:342)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:208)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:113)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:148)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
</Trace>
</Error>
</soapetail>
</soap:Fault>

com.zimbra.common.soap.SoapFaultException: invalid request: Request must have allDay="1" if using a DATE start time instead of DATETIME
ExceptionId:com.zimbra.common.service.ServiceExcep tion: invalid request: Request must have allDay="1" if using a DATE start time instead of DATETIME
Code:service.INVALID_REQUEST
at com.zimbra.common.service.ServiceException.INVALID _REQUEST(ServiceException.java:190)
at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teElementCommon(CalendarUtils.java:758)
at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teForCancel(CalendarUtils.java:259)
at com.zimbra.cs.service.mail.SetCalendarItem$SetCale ndarItemInviteParser.parseInviteElement(SetCalenda rItem.java:72)
at com.zimbra.cs.service.mail.ParseMimeMessage$Invite Parser.parse(ParseMimeMessage.java:129)
at com.zimbra.cs.service.mail.SetCalendarItem.getSetC alendarItemData(SetCalendarItem.java:150)
at com.zimbra.cs.service.mail.SetCalendarItem.parseSe tAppointmentRequest(SetCalendarItem.java:216)
at com.zimbra.cs.service.mail.SetCalendarItem.handle( SetCalendarItem.java:97)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:342)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:208)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:113)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:148)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)

Code:service.INVALID_REQUEST
at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88)
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:245)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:221)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:251)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:297)
at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:284)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:660)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:640)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:636)
at com.zimbra.cs.mailbox.PushChanges.syncCalendarItem (PushChanges.java:1121)
at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges .java:272)
at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges .java:173)
at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync .java:195)
at com.zimbra.cs.mailbox.OfflineMailbox.sync(OfflineM ailbox.java:115)
at com.zimbra.cs.mailbox.OfflineMailbox.syncOnTimer(O fflineMailbox.java:96)
at com.zimbra.cs.mailbox.DesktopMailbox$1.run(Desktop Mailbox.java:117)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

----------------------------------------------------------------------------
Reply With Quote
Reply

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.