Cannot access Agile boards and View Boards page keeps loading without any error message
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Cannot access Agile boards and the View Boards page just loads without any error message.
Environment
Jira DC
Diagnosis
The View Board pages (Agile and Scrum) does not load. The page shows wait symbol but does not show any error message.
When we look into 'atlassian-jira.log' file, we see DB related error message.
We can see SQLServerException: Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup error message.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 282024-10-07 06:38:21,107+0100 https-jsse-nio-8443-exec-2176 url: /plugins/servlet/project-config/PROJECT-KEY/summary; user: xxxxxx ERROR xxxxxx /plugins/servlet/project-config/PROJECT-KEY/summary [o.a.c.c.C.[Catalina].[localhost].[/]] Unhandled exception occurred whilst decorating page java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy4490.getAll(Unknown Source) at com.atlassian.greenhopper.service.rapid.ProjectRapidViewServiceImpl.findRapidViewsByProject(ProjectRapidViewServiceImpl.java:43) at com.atlassian.greenhopper.web.sidebar.BoardListHelper.getProjectBoards(BoardListHelper.java:68) at com.atlassian.greenhopper.web.sidebar.BoardListHelper.selectBoard(BoardListHelper.java:120) at com.atlassian.greenhopper.web.sidebar.BoardScopeFilterContextProviderImpl.lambda$findSelectedBoard$0(BoardScopeFilterContextProviderImpl.java:90) at io.atlassian.fugue.Option$None.fold(Option.java:393) at io.atlassian.fugue.Option.orElse(Option.java:218) at com.atlassian.greenhopper.web.sidebar.BoardScopeFilterContextProviderImpl.findSelectedBoard(BoardScopeFilterContextProviderImpl.java:90) --------------- Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor4037.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.atlassian.activeobjects.tx.TransactionalProxy.invoke(TransactionalProxy.java:60) at com.atlassian.activeobjects.tx.TransactionalProxy.invoke(TransactionalProxy.java:33) Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library: Database: - name:Microsoft SQL Server - version:11.00.7507 - minor version:0 - major version:11 - name:Microsoft JDBC Driver 7.2 for SQL Server - version:7.2.1.0 com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.stream(EntityManagedActiveObjects.java:174) at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects.stream(TenantAwareActiveObjects.java:311)
Cause
This error is observed when your 'tempDB' of MSSQL DB runs out of space. It's possible that this can effect multiple functionalities on the Jira instance.
The below articles from Microsoft provides more information about this error message.
Solution
We suggest to get in touch with the DBA/DB team to fix the space issue related to the tempdb errors on MSSQL Server, which hosts the Jira database.
Was this helpful?