Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

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 08-08-2011, 08:50 AM
Senior Member
 
Posts: 59
Default CreateMountpointRequest PERM_DENIED when sharing calendars

Hi,

I've had a few reports now of users that get errors when accepting a calendar share request. Server is running 7.1.1 NE

The logged error is:

2011-08-08 15:21:01,343 INFO [btpool0-1504://zimbra.PROTECTED.TLD/service/soap/CreateMountpointRequest] [name=user.one@PROTECTED.TLD;mid=72;ip=
XX.XX.XX.XX;ua=Zimbra Desktop/7.0.1_10791_Windows;via=127.0.0.1(ZimbraWebClient - PRISM (Win)/0.0);] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: permission denied: you do not have sufficient permissions
ExceptionId:btpool0-1504://zimbra.PROTECTED.TLD/service/soap/CreateMountpointRequest:1312809661343:01ed5607ae07 88a6
Code:service.PERM_DENIED
at com.zimbra.common.service.ServiceException.PERM_DE NIED(ServiceException.java:278)
at com.zimbra.cs.mailbox.Mailbox.checkAccess(Mailbox. java:1907)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox. java:2055)
at com.zimbra.cs.mailbox.Mailbox.getFolderById(Mailbo x.java:2913)
at com.zimbra.cs.mailbox.Mailbox.getFolderTree(Mailbo x.java:3038)
at com.zimbra.cs.service.mail.GetFolder.handle(GetFol der.java:86)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412)
at com.zimbra.soap.DocumentHandler.proxyRequest(Docum entHandler.java:465)
at com.zimbra.soap.DocumentHandler.proxyRequest(Docum entHandler.java:436)
at com.zimbra.cs.service.mail.CreateMountpoint.fetchR emoteFolder(CreateMountpoint.java:119)
at com.zimbra.cs.service.mail.CreateMountpoint.handle (CreateMountpoint.java:78)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:725)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:155)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Reply With Quote
  #2 (permalink)  
Old 08-08-2011, 11:34 PM
Zimbra Employee
 
Posts: 70
Default

Can you double check the sharing properties of the shared calendar and check if user.one@PROTECTED.TLD has access to it?
Reply With Quote
  #3 (permalink)  
Old 08-09-2011, 12:05 AM
Senior Member
 
Posts: 59
Default

Yes, the other user is listed as "Viewer"... Often removing the share and sharing again does the trick.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

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




 

SEO by vBSEO ©2011, Crawlability, Inc.