Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Desktop > Error Reports

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 10-31-2010, 12:50 PM
Starter Member
 
Posts: 2
Default Zimbra fetching email but displays error when clicking on message/inbox

Zimbra is working fine for most my two other email addresses (gmail and yahoo) but doesnt work for my corporate email (MS exchange).

If fetches messages properly (i see them in my inbox) but when I click on it to read the message, it displays the following error:



A network service error has occurred.
method: SearchRequest
msg: system failure: fetching search metadata
code: service.FAILURE
detail: soap:Receiver
trace: com.zimbra.common.service.ServiceException: system failure: fetching search metadata ExceptionId:btpool0-9:1288553945866:40b3404dd6d6c47e 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.(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.DebugConnection.prepareStatement( DebugConnection.java:37) 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
request:

anyone else had this problem?

thanks
Reply With Quote
  #2 (permalink)  
Old 03-23-2011, 01:29 AM
Starter Member
 
Posts: 2
Default

Yes
Win XP,
Zimbra 7.0 (10706)

Removed my email from the error

A network service error has occurred.
method: [unknown]
msg: system failure: fetching search metadata
code: service.FAILURE
detail: soap:Receiver
trace: com.zimbra.common.service.ServiceException: system failure: fetching search metadata ExceptionId:btpool0-8:1300868682270:c395c9c578328f7c Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248) at com.zimbra.cs.db.DbSearch.searchInternal(DbSearch. java:769) at com.zimbra.cs.db.DbSearch.search(DbSearch.java:581 ) at com.zimbra.cs.index.DBQueryOperation$1.doInTransac tion(DBQueryOperation.java:754) at com.zimbra.cs.mailbox.Mailbox.execute(Mailbox.java :2294) at com.zimbra.cs.index.DBQueryOperation.fetch(DBQuery Operation.java:751) at com.zimbra.cs.index.DBQueryOperation.noLuceneGetNe xtChunk(DBQueryOperation.java:797) at com.zimbra.cs.index.DBQueryOperation.getNextChunk( DBQueryOperation.java:1036) at com.zimbra.cs.index.DBQueryOperation.peekNext(DBQu eryOperation.java:540) at com.zimbra.cs.index.QueryOperation.hasNext(QueryOp eration.java:173) at com.zimbra.cs.index.ItemPreloadingGrouper.bufferHi ts(ItemPreloadingGrouper.java:53) at com.zimbra.cs.index.BufferingResultsGrouper.hasNex t(BufferingResultsGrouper.java:61) at com.zimbra.cs.index.MsgQueryResults.internalGetNex tHit(MsgQueryResults.java:57) at com.zimbra.cs.index.MsgQueryResults.bufferNextHit( MsgQueryResults.java:95) at com.zimbra.cs.index.MsgQueryResults.peekNext(MsgQu eryResults.java:118) at com.zimbra.cs.index.ZimbraQueryResultsImpl.hasNext (ZimbraQueryResultsImpl.java:95) at com.zimbra.cs.index.HitIdGrouper.bufferHits(HitIdG rouper.java:59) at com.zimbra.cs.index.BufferingResultsGrouper.peekNe xt(BufferingResultsGrouper.java:70) 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.service.mail.SearchConv.putHits(Sear chConv.java:199) at com.zimbra.cs.service.mail.SearchConv.handle(Searc hConv.java:117) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:401) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:276) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:157) 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:727) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208) 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: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.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) 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.(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:39) at com.zimbra.cs.db.AbstractRetry.doRetry(AbstractRet ry.java:60) at com.zimbra.cs.db.RetryConnection.prepareStatement( RetryConnection.java:43) at org.apache.commons.dbcp.DelegatingConnection.prepa reStatement(DelegatingConnection.java:281) at org.apache.commons.dbcp.PoolingDataSource$PoolGuar dConnectionWrapper.prepareStatement(PoolingDataSou rce.java:313) at com.zimbra.cs.db.DbPool$Connection.prepareStatemen t(DbPool.java:105) at com.zimbra.cs.db.DbSearch.searchInternal(DbSearch. java:720) ... 47 more
request:

Body: {
SearchConvRequest: {
_jsns: "urn:zimbraMail",
cid: "eabbd7a0-d84b-4eb9-bf23-63f2075061fd:-68168",
fetch: "eabbd7a0-d84b-4eb9-bf23-63f2075061fd:68168",
html: 1,
limit: 250,
locale: {
_content: "en_GB"
},
max: 100000,
needExp: 1,
offset: 0,
query: "in:"inbox"",
read: 1,
sortBy: "dateDesc",
tz: {
id: "Europe/London"
}
}
},
Header: {
context: {
_jsns: "urn:zimbra",
account: {
_content: "XXXXXX@XXXXXX",
by: "name"
},
authToken: "(removed)",
notify: {
seq: 43
},
session: {
_content: 18,
id: 18
},
userAgent: {
name: "ZimbraWebClient - PRISM (Win)",
version: "0.0"
}
}
}
Reply With Quote
  #3 (permalink)  
Old 03-23-2011, 09:09 AM
Starter Member
 
Posts: 2
Default

I never found the issue and there's no activity - I moved on since then (removed the software).

good luck!
Reply With Quote
  #4 (permalink)  
Old 03-24-2011, 05:37 AM
Starter Member
 
Posts: 2
Default

I did a 'reindex' within the setup but didnt resolve the issue.

I ran a 'reset' (and had a good nights sleep) which seems to have resolved the issue. I Still dont know the cause though
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.