Error in Admin Console after update to 7.1.12

[dik23]

Last night I updated from v6 to 7.1.2. As there's no notebook in v7 I deleted the documents account before running the update.

Now whenever I'm greeted with a popup every time I go to Admin Console > Configuration > Domains > my.domain

Account does not exist

Message: no such account: documents@my.domain Error code: account.NO_SUCH_ACCOUNT Method: [unknown] Details:soap:Sender

I choose OK and continue with no noticeable ill effect, apart from it's annoying.

In mailbox.log I get :

WARN  [btpool0-564://my.domain:7071/service/admin/soap/GetFolderRequest] [ip=xxx.xxx.xxx.xxx;] SoapEngine - unable to construct SOAP context
com.zimbra.cs.account.AccountServiceException: no such account: documents@my.domain
ExceptionId:btpool0-564://my.domain:7071/service/admin/soap/GetFolderRequest:1316617538649:609a091358ba5722
Code:account.NO_SUCH_ACCOUNT
	at com.zimbra.cs.account.AccountServiceException.NO_SUCH_ACCOUNT(AccountServiceException.java:187)
	at com.zimbra.soap.ZimbraSoapContext.<init>(ZimbraSoapContext.java:266)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:202)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
	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.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
	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:218)
	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: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(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:946)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
	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:410)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

I have tried recreating the documents@my.domain account and then deleting it again but it has no effect.

Any ideas ?

[dik23]

Doesn't anyone have any ideas on this ?

[dik23]

Updated to 7.1.3_GA_3346.UBUNTU8_64 UBUNTU8_64 , Patch 7.1.3_P1 and still getting this on both FOSS and NE.

Also when I go to Accounts and click on an account I get an error popup and pretty much an identical section logged in mailbox.log

I can't believe I'm the only one getting this error because it's on two separate instances of Zimbra and the error is complaining about the lack of a documents account, which was removed on update from Zim6 > 7.

Does anyone have any ideas on this at all ?

[phoenix]

How about some of the solutions in the forums: site:zimbra.com +"documents account" - Yahoo! Search Results

[dik23]

Got it now ! Thanks for making my brain do something that it wasn't doing before. I'd been occasionally searching for the answer to this for a while.

In case anyone else comes across this do the following as zimbra :

zmprov md example.com zimbraNotebookAccount ""

Although what I still don't understand is why this wasn't done by the update and why I have to do it manually. Oh well fixed now and that's all that really matters I suppose.

[phoenix]

It should have done this during the upgrade as it migrated the 'Documents' (now defunct) to the Briefcase, I have seen a couple of reports of a couple of hiccups, I guess this is one of them. Anyway, glad you've fixed it.