Stash can't be started due to the transaction log for database is full

Troubleshooting Databases

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This article only applies to Atlassian's server products. Learn more about the differences between cloud and server.

This Knowledge Base article was written specifically for the Atlassian Server platform and may be self applied. Atlassian Cloud customers may create a support request referencing this article to have the solution applied on your behalf by Atlassian Support.


Starting Stash fails with the following message on the UI:

SpringMVC dispatcher [springMvc] could not be started

The following is seen on atlassian-stash.log:

09-Jun-2015 09:54:04.048 SEVERE [http-nio-7990-exec-1] org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for servlet springMvc threw exception
 com.atlassian.stash.exception.DataStoreException: A database error has occurred.
Caused by: org.springframework.dao.InvalidDataAccessResourceUsageException: could not execute batch; SQL [update cwd_user set user_name=?, lower_user_name=?, is_active=?, created_date=?, updated_date=?, first_name=?, lower_first_name=?, last_name=?, lower_last_name=?, display_name=?, lower_display_name=?, email_address=?, lower_email_address=?, external_id=?, directory_id=?, credential=? where id=?]; nested exception is org.hibernate.exception.SQLGrammarException: could not execute batch
Caused by: org.hibernate.exception.SQLGrammarException: could not execute batch
Caused by: The transaction log for database 'stash' is full due to 'LOG_BACKUP'. 


The problem is on your Microsoft SQL database that contains a full table.


Check the guide below for Microsoft SQL to fix your database and restart Stash.

Last modified on Apr 6, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.