After opening the first time, ZD is stuck on loading forever.

[IvoryKnight]

I am trying to connect to Microsoft Exchange Server 2003. The first time I opened the program, everything worked fine as it was still loading. I closed the program and let it load in the background. When I tried opening it again, it got stuck on the Loading screen. I waited for hours, but it didn't get anywhere. I suspect that there is an issue with our server having too many folders in the Public Folders. Is there anything I can change to fix this?

...960KB of folder opening...

2010-12-22 09:36:03,567 INFO  [sync-manager-init] [] mailbox - "Tasks": Decoded metadata folder counts (c0/d0/u0/du0/s0) i4ms:1
2010-12-22 09:36:03,567 INFO  [sync-manager-init] [] mailbox - "Junk": Decoded metadata folder counts (c0/d0/u0/du0/s0) i4ms:1
2010-12-22 09:36:03,567 INFO  [sync-manager-init] [] mailbox - "Drafts": Decoded metadata folder counts (c0/d0/u0/du0/s0) i4ms:1
2010-12-22 09:36:10,973 WARN  [btpool0-3] [mid=2;] misc - system failure: fetching search metadata
com.zimbra.common.service.ServiceException: system failure: fetching search metadata
ExceptionId:btpool0-3:1293032170973:67e1cec0de33d270
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.noLuceneGetNextChunk(DBQueryOperation.java:850)
	at com.zimbra.cs.index.DBQueryOperation.getNextChunk(DBQueryOperation.java:1101)
	at com.zimbra.cs.index.DBQueryOperation.peekNext(DBQueryOperation.java:625)
	at com.zimbra.cs.index.QueryOperation.hasNext(QueryOperation.java:159)
	at com.zimbra.cs.index.ItemPreloadingGrouper.bufferHits(ItemPreloadingGrouper.java:51)
	at com.zimbra.cs.index.BufferingResultsGrouper.hasNext(BufferingResultsGrouper.java:60)
	at com.zimbra.cs.index.ConvQueryResults.internalGetNextHit(ConvQueryResults.java:55)
	at com.zimbra.cs.index.ConvQueryResults.bufferNextHit(ConvQueryResults.java:112)
	at com.zimbra.cs.index.ConvQueryResults.peekNext(ConvQueryResults.java:118)
	at com.zimbra.cs.index.ZimbraQueryResultsImpl.hasNext(ZimbraQueryResultsImpl.java:70)
	at com.zimbra.cs.index.ItemPreloadingGrouper.bufferHits(ItemPreloadingGrouper.java:51)
	at com.zimbra.cs.index.BufferingResultsGrouper.hasNext(BufferingResultsGrouper.java:60)
	at com.zimbra.cs.index.HitIdGrouper.bufferHits(HitIdGrouper.java:63)
	at com.zimbra.cs.index.BufferingResultsGrouper.peekNext(BufferingResultsGrouper.java:69)
	at com.zimbra.cs.index.FilteredQueryResults.peekNext(FilteredQueryResults.java:132)
	at com.zimbra.cs.index.FilteredQueryResults.hasNext(FilteredQueryResults.java:102)
	at com.zimbra.cs.index.ResultsPager.hasNext(ResultsPager.java:151)
	at com.zimbra.cs.service.mail.Search.putHits(Search.java:200)
	at com.zimbra.cs.service.mail.Search.handle(Search.java:127)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
	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.handle(ServletHandler.java:390)
	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.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:218)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:413)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(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(RetryConnection.java:23)
	at com.zimbra.cs.db.AbstractRetry.doRetry(AbstractRetry.java:44)
	at com.zimbra.cs.db.RetryConnection.prepareStatement(RetryConnection.java:27)
	at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:248)
	at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:302)
	at com.zimbra.cs.db.DbPool$Connection.prepareStatement(DbPool.java:105)
	at com.zimbra.cs.db.DbSearch.searchInternal(DbSearch.java:710)
	... 47 more