[SOLVED] com.zimbra.cs.account.AccountServiceException: account is not active

[mackoftrack]

I've been getting these errors in /opt/zimbra/log/mailbox.log for quite some time. They seem to be related to ZCO.

2009-09-08 13:10:56,539 WARN  [btpool0-184] [aname=xxxxx@xxxxxxx.com;ip=xxx.xxx.xxx.xxx;ua=ZimbraConnectorForOutlook/5.0.3064.18;id=df6d232f-9093-4fa9-b099-0ca594320e2a;] SoapEngine - target account is not active
com.zimbra.cs.account.AccountServiceException: account is not active:df6d232f-9093-4fa9-b099-0ca594320e2a
ExceptionId:btpool0-184:1252440656539:29ce3259eca654bc
Code:account.ACCOUNT_INACTIVE
        at com.zimbra.cs.account.AccountServiceException.ACCOUNT_INACTIVE(AccountServiceException.java:285)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:411)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:275)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:187)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:145)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(HandlerWrapper.java:139)
        at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:350)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.Server.handle(Server.java:313)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

Running ZCS NE 5.0.18, ZCO 5.0.18. The accounts in question are *not* inactive.

Any ideas? Thanks!

[fsiegel]

Well -- the server sure thinks it is. Did the account GUID change? Did you try creating a new profile in ZCO and seeing what happens?

[mackoftrack]

how/why would the GUID have changed?
is it absolutely necessary that i recreate the profile?
i am getting these errors for several active accounts.

thanks

[mackoftrack]

BTW, here is the output of zimbraAccountStatus for the account in question:

[zimbra@zimbra ~]$ zmprov ga xxxxx@mydomain.com zimbraAccountStatus
# name xxxxx@mydomain.com
zimbraAccountStatus: active

[fsiegel]

Do you have a zco log for this? If so, please post.

[mackoftrack]

where do i find the ZCO log?

[fsiegel]

You have to enable zco logging via zcologctl.exe, which is in the same directory as your dlls. Enable http logging and regular logging - that's it. You can determine where the logs go.

[mackoftrack]

I figured it out. The errors were being caused by shared mailboxes in Outlook that had become stale for some reason.
To fix, I closed the shared mailboxes, and then reopened them.

[fsiegel]

Thanks. I'll remember this for future reference.

[mfvm]

I figured it out. The errors were being caused by shared mailboxes in Outlook that had become stale for some reason.
To fix, I closed the shared mailboxes, and then reopened them.

A small addition: »stale for some reason« may be a shared folder of a deleted user - I just saw that. The obvious fix is to close the related folder in Outlook.