Zimbra Desktop 2.0beta1 won't start up

[davidfraser]

I had Zimbra Desktop 2.0 beta1 working beautifully, now it has hit an error that prevents it from starting up:

system - Unable to commit database transaction.  Forcing server to abort.
com.zimbra.common.service.ServiceException: system failure: committing database transaction
ExceptionId:sync-mbox-xxxxxx@xxxxxx.com:1267555756033:18cefba855277d37
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
        at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.java:124)
        at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailbox.java:6737)
        at com.zimbra.cs.mailbox.Mailbox.optimize(Mailbox.java:6519)
        at com.zimbra.cs.mailbox.SyncMailbox$1.run(SyncMailbox.java:257)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)
Caused by: java.sql.SQLException: database in auto-commit mode
        at org.sqlite.Conn.commit(Conn.java:389)
        at com.zimbra.cs.db.DebugConnection.commit(DebugConnection.java:42)
        at org.apache.commons.dbcp.DelegatingConnection.commit(DelegatingConnection.java:301)
        at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.commit(PoolingDataSource.java:200)
        at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.java:122)
        ... 5 more

I'll attach the full log - this doesn't always happen straight away, but when it does happen, it stops the (local zimbra desktop) server dead

[davidfraser]

More details at Bug 44988 – sqlite database commit error forces desktop server process to stop

[Franck]

I fixed it like this:
How to recover from SQLite corruption on Zimbra Desktop : Avonsys