How can you get a "network error" accessing the local folders?

[fhouston]

I have a user (using v2.0 of the desktop on a Win7 machine) who has been migrating a bunch of old email to the local folders. Sometime last week, he is not sure when, he lost access to the mail that had already been moved over. He can move more mail to the local folders, he just can't access what is there. Whenever he tries he gets a "network service error". The two attachments show what he is seeing. The below is the info I pulled from the local Zimbra log that I believe corresponds to the error.

Anyone have any idea what is going on? How does one get a "network error" accessing local folders Although I suspect it is more of a generic error code. If I had to take a guess I believe the index has potentially been corrupted somehow. I was able to dig into the file structure (User/AppData/Local/Zimbra....) and verify the .msg files themselves still seem to be there so I don't think any data was lost, just the index/metadata. Any way to force a rebuild?

Any hints/clues/suggestions are appreciated....



2011-04-22 13:21:59,392 WARN [btpool0-1] [mid=1;] misc - system failure: fetching search metadata
com.zimbra.common.service.ServiceException: system failure: fetching search metadata
ExceptionId:btpool0-1:1303492919392:4cef8b9293d66433
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.cs.db.DbSearch.searchInternal(DbSearch. java:759)
at com.zimbra.cs.db.DbSearch.search(DbSearch.java:572 )
at com.zimbra.cs.index.DBQueryOperation.noLuceneGetNe xtChunk(DBQueryOperation.java:850)
at com.zimbra.cs.index.DBQueryOperation.getNextChunk( DBQueryOperation.java:1101)
at com.zimbra.cs.index.DBQueryOperation.peekNext(DBQu eryOperation.java:625)
at com.zimbra.cs.index.QueryOperation.hasNext(QueryOp eration.java:159)
at com.zimbra.cs.index.ItemPreloadingGrouper.bufferHi ts(ItemPreloadingGrouper.java:51)
at com.zimbra.cs.index.BufferingResultsGrouper.hasNex t(BufferingResultsGrouper.java:60)
at com.zimbra.cs.index.ConvQueryResults.internalGetNe xtHit(ConvQueryResults.java:55)
at com.zimbra.cs.index.ConvQueryResults.bufferNextHit (ConvQueryResults.java:112)
at com.zimbra.cs.index.ConvQueryResults.peekNext(Conv QueryResults.java:118)
at com.zimbra.cs.index.ZimbraQueryResultsImpl.hasNext (ZimbraQueryResultsImpl.java:70)
at com.zimbra.cs.index.ItemPreloadingGrouper.bufferHi ts(ItemPreloadingGrouper.java:51)
at com.zimbra.cs.index.BufferingResultsGrouper.hasNex t(BufferingResultsGrouper.java:60)
at com.zimbra.cs.index.HitIdGrouper.bufferHits(HitIdG rouper.java:63)
at com.zimbra.cs.index.BufferingResultsGrouper.peekNe xt(BufferingResultsGrouper.java:69)
at com.zimbra.cs.index.FilteredQueryResults.peekNext( FilteredQueryResults.java:132)
at com.zimbra.cs.index.FilteredQueryResults.hasNext(F ilteredQueryResults.java:102)
at com.zimbra.cs.index.ResultsPager.hasNext(ResultsPa ger.java:151)
at com.zimbra.cs.service.mail.Search.putHits(Search.j ava:200)
at com.zimbra.cs.service.mail.Search.handle(Search.ja va:127)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:420)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:274)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
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: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(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.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:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
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:413)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (too many SQL variables)
at org.sqlite.DB.newSQLException(DB.java:374)
at org.sqlite.DB.newSQLException(DB.java:378)
at org.sqlite.DB.throwex(DB.java:365)
at org.sqlite.NativeDB.prepare(Native Method)
at org.sqlite.DB.prepare(DB.java:123)
at org.sqlite.PrepStmt.<init>(PrepStmt.java:44)
at org.sqlite.Conn.prepareStatement(Conn.java:403)
at org.sqlite.Conn.prepareStatement(Conn.java:398)
at org.sqlite.Conn.prepareStatement(Conn.java:382)
at com.zimbra.cs.db.RetryConnection$1.execute(RetryCo nnection.java:23)
at com.zimbra.cs.db.AbstractRetry.doRetry(AbstractRet ry.java:44)
at com.zimbra.cs.db.RetryConnection.prepareStatement( RetryConnection.java:27)
at org.apache.commons.dbcp.DelegatingConnection.prepa reStatement(DelegatingConnection.java:248)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuar dConnectionWrapper.prepareStatement(PoolingDataSou rce.java:302)
at com.zimbra.cs.db.DbPool$Connection.prepareStatemen t(DbPool.java:105)
at com.zimbra.cs.db.DbSearch.searchInternal(DbSearch. java:710)
... 47 more

[fhouston]

Just a quick update... the user tried the "reindex" function on the main setup screen of Zimbra desktop and that did not help/resolve the issue. Anyone have any hints/clues/suggestions? This really is a show stopper for this user...

I know one trick we used to do for Eudora (I think that's what it was) was to delete the index files (.toc files IIRC) and that would force a reindex the next time the mail box was accessed. Is there a similar file in the Zimbra structure?




RESOLUTION: I'm still not sure what caused the issue, but upgrading to Desktop v7 resolved it... If someone can still answer the question above (about whether or not index files can be individually deleted and where they can be found) that would be appreciated for future reference.

TIA



DERESOLUTION Although he can access the email now, ALL the messages in ALL the folders under the Local Folders have lost their directory structure, for lack of a better phrase. What I mean is no matter which of the folders under local folders you click on you get the exact same message list. It seems to be a complete list so again I don't think any data was lost, but which message belongs in which folder is completely gone. Any way to recover this?

[jflanigan]

The original problem sounds like a variation on Bug 54935 - Zimbra is stuck loading forever when trying to connect to an Exchange server with tons of public folders. Most likely this caused messages not to be placed in their correct folder when moved.

I don't think there is any way to recover the missing/incorrect folder structure.

As for your question about reindexing; the reindex function on the account setup page does all that is required/possible. There is no need to manually manipulate index files.