Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > ZCS Client Connectors > Zimbra Connector for Outlook

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 05-30-2010, 05:02 PM
Active Member
 
Posts: 36
Default [SOLVED] Server failures on shared inbox

Configuration:
Outlook 2007 with Outlook connector 6.0.5
Server on ubuntu 8, zimbra 6.0.5

Hi,

Several users are sharing a common generic mailbox and are starting to get a lot of server failures:

here is the error_report.xml:
Code:
<SyncError>
−
<Request>
−
<soap:Envelope>
−
<soap:Header>
−
<context>
<userAgent name="ZimbraConnectorForOutlook" version="6.0.5846.5"/>
<nonotify/>
<noqualify/>
<account by="id">fae9bb6b-33b6-4090-85f3-921143fb501f</account>
−
<authToken>
0_360ed6edffc0c214edb1b5809956859d02cb8e8c_69643d33363a36346431626536622d386635382d343637332d626332652d3035326162663637623564373b6578703d31333a313237353433343134393135363b76763d313a303b747970653d363a7a696d6272613b
</authToken>
<nosession/>
</context>
</soap:Header>
−
<soap:Body>
−
<SaveDraftRequest>
<m aid="ab01bded-6895-4fc9-bc8c-f6ece6154ced:74add517-8a41-4505-b42c-323a9fffd19a" id="8427"/>
</SaveDraftRequest>
</soap:Body>
</soap:Envelope>
</Request>
−
<Response>
−
<soap:Envelope>
−
<soap:Header>
−
<context>
<change acct="fae9bb6b-33b6-4090-85f3-921143fb501f" token="31270"/>
</context>
</soap:Header>
−
<soap:Body>
−
<soap:Fault>
−
<soap:Code>
<soap:Value>soap:Sender</soap:Value>
</soap:Code>
−
<soap:Reason>
<soap:Text>cannot modify immutable object: 8427</soap:Text>
</soap:Reason>
−
<soap:Detail>
−
<Error>
<Code>mail.IMMUTABLE_OBJECT</Code>
−
<Trace>
btpool0-30526://<server>/service/soap/SaveDraftRequest:1275261518488:734f8e76bdd44e92
</Trace>
<a t="IID" n="itemId">8427</a>
</Error>
</soap:Detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
</Response>
</SyncError>
and the message:
Code:
Server Failures were detected.  No action is required.
This e-mail was generated for technical support purposes.
Please see the attached files for more details about the problems encountered.

Computer Name: WS43

Version: 6.0.5846.5

Parent Folder EID: 00000000bfc19fdaadcde84a8f8b25c92ef6f3d6a2800000

Parent Folder Name: Inbox

Parent Folder ID: 2

Target Object EID: 00000000bfc19fdaadcde84a8f8b25c92ef6f3d664d32000

Store: Zimbra - Mail
I suspect someone tried to save a draft in the shared folder, but is there a way for me to trace which computer is causing it? (if it's actually caused by outlook?)
Reply With Quote
  #2 (permalink)  
Old 05-30-2010, 05:15 PM
Active Member
 
Posts: 36
Default

sorry, forgot to add the server logs:

Code:
2010-05-31 09:18:44,237 INFO  [btpool0-30530://<server>/service/soap/SaveDraftRequest] [name=mail@<server>;aname=<other_user>@<server>;mid=137;ip=<snip>;ua=ZimbraConnectorForOutlook/6.0.5846.5;] soap - Save
DraftRequest
2010-05-31 09:18:44,245 INFO  [btpool0-30530://<server>/service/soap/SaveDraftRequest] [name=mail@<server>;aname=<other_user>@<server>;mid=137;ip=<snip>;ua=ZimbraConnectorForOutlook/6.0.5846.5;] SoapEngine
- handler exception
com.zimbra.cs.mailbox.MailServiceException: cannot modify immutable object: 8432
ExceptionId:btpool0-30530://<server>/service/soap/SaveDraftRequest:1275261524245:734f8e76bdd44e92
Code:mail.IMMUTABLE_OBJECT Arg:(itemId, IID, "8432")
        at com.zimbra.cs.mailbox.MailServiceException.IMMUTABLE_OBJECT(MailServiceException.java:379)
        at com.zimbra.cs.mailbox.Mailbox.saveDraft(Mailbox.java:4710)
        at com.zimbra.cs.service.mail.SaveDraft.handle(SaveDraft.java:116)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:419)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:273)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:157)
        at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
        at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.servlet.other_userAgentFilter.doFilter(other_userAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:155)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        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(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
2010-05-31 09:18:44,364 INFO  [btpool0-30530://<server>/service/soap/SyncRequest] [name=mail@<server>;aname=<other_user>@<server>;mid=137;ip=150.101.221.156;ua=ZimbraConnectorForOutlook/6.0.5846.5;] soap - SyncReque
st
Reply With Quote
  #3 (permalink)  
Old 05-31-2010, 08:25 PM
Active Member
 
Posts: 36
Default

Update on this issue:

Giving full write access to the shared inbox drafts folder (using the CLI) seems to "stop" the error messages. (didn't get one so far, as opposed to dozens a day)

Problem is, doing so for a dozen or so shared inboxes access by 5+ users is not all that convenient.

Any tips or insight on that?
Reply With Quote
  #4 (permalink)  
Old 06-03-2010, 05:13 PM
Active Member
 
Posts: 36
Default

Any idea, anyone?
Reply With Quote
  #5 (permalink)  
Old 06-04-2010, 06:38 AM
Zimbra Employee
 
Posts: 1,327
Default

Haven't been able to repro this yet with my test server. I tried giving reviewer permission to inbox and drafts. Can you give me the exact steps?

You may know this by now, but server log shows which user causes the issue:

INFO [btpool0-30530://<server>/service/soap/SaveDraftRequest]
[name=mail@<server>;aname=<other_user>@<server;
mid=137;ip=<snip>;ua=ZimbraConnectorForOutlook/6.0.5846.5;] soap - Save
DraftRequest
Reply With Quote
  #6 (permalink)  
Old 06-20-2010, 06:27 PM
Active Member
 
Posts: 36
Default

I can't reproduce it myself.

I usually go on the server logs, look for the users and target inbox involved with the save draft error and manually give write access on the target inbox.

My guess is it is caused by the automatic draft saving function of outlook. None of the users tried to save drafts at any point.
Reply With Quote
  #7 (permalink)  
Old 05-19-2011, 09:19 PM
Active Member
 
Posts: 36
Default

My problem was apparently caused by the antivirus trying to edit the body of the message to add a "scanned" tag.
Reply With Quote
  #8 (permalink)  
Old 07-08-2011, 12:16 PM
Active Member
 
Posts: 32
Default Having he same problem

Could you tell me how you managed to fix it exactly, what steps you took?
Thank you.

I am very new to this zimbra and Linux as a whole..so I really appreciate any help.

Thanks again
Reply With Quote
  #9 (permalink)  
Old 07-08-2011, 12:20 PM
Zimbra Consultant & Moderator
 
Posts: 20,319
Default

Quote:
Originally Posted by crawlspace35 View Post
Could you tell me how you managed to fix it exactly, what steps you took?
The answer is in the post above yours, it was the a/v on his system. It's not good having an a/v system scan and modify the email.
__________________
Regards


Bill
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.