Hello Inflectra support team, Recently a significant amount of timeout errors have been registered in the Spirateam log. An error occurred while executing the command definition. See the inner exception for details. In APPLICATION.Web.Services.Ajax.Json.SpiraErrorHandler::ProvideFault: Messages: An error occurred while executing the command definition. See the inner exception for details. [System.Data.EntityCommandExecutionException] Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. [System.Data.SqlClient.SqlException] The wait operation timed out [System.ComponentModel.Win32Exception] Stack Trace: at System.Data.EntityClient.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) at System.Data.Objects.ObjectContext.CreateFunctionObjectResult[TElement](EntityCommand entityCommand, ReadOnlyMetadataCollection`1 entitySets, EdmType[] edmTypes, MergeOption mergeOption) at System.Data.Objects.ObjectContext.ExecuteFunction[TElement](String functionName, MergeOption mergeOption, ObjectParameter[] parameters) at APPLICATION.Business.SpiraTestEntities.TestCase_RetrieveParentFolders(Nullable`1 projectId, Nullable`1 folderId, Nullable`1 isIncludeSelf) at APPLICATION.Business.TestCaseManager.TestCaseFolder_GetParents(Int32 projectId, Int32 testFolderId, Boolean includeSelf) at APPLICATION.Web.Services.Ajax.TestSetTestCaseService.RetrieveNameDesc(Nullable`1 projectId, Int32 testSetTestCaseId, Nullable`1 displayTypeId) at SyncInvokeRetrieveNameDesc(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet) I tried to fix the problem by rebuilding indexes, but it had no effect. Spirateam version 6.2.0.1 MS SQL Server 2014 Standard (64) Windows Server 2019 Standard edition, 24 GB, processors 6, Intel Xeon 4216 2.1 GHz en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/2895.aspxthreadId=2895Svetoslav SARAKINOV (Svetoslav.SARAKINOV@amadeus.com) Hello Inflectra support team, Recently a significant amount of timeout errors have been registered in the Spirateam log. An error occurred while executing the command definition. See the inner exception for details. In APPLICATION.Web.Services.Ajax.Json.SpiraErrorHandler::ProvideFault: Messages: An error occurred while executing the command definition. See the inner exception for details. [System.Data.EntityCommandExecutionException] Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. [System.Data.SqlClient.SqlException] The wait operation timed out [System.ComponentModel.Win32Exception] Stack Trace: at System.Data.EntityClient.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) at System.Data.Objects.ObjectContext.CreateFunctionObjectResult[TElement](EntityCommand entityCommand, ReadOnlyMetadataCollection`1 entitySets, EdmType[] edmTypes, MergeOption mergeOption) at System.Data.Objects.ObjectContext.ExecuteFunction[TElement](String functionName, MergeOption mergeOption, ObjectParameter[] parameters) at APPLICATION.Business.SpiraTestEntities.TestCase_RetrieveParentFolders(Nullable`1 projectId, Nullable`1 folderId, Nullable`1 isIncludeSelf) at APPLICATION.Business.TestCaseManager.TestCaseFolder_GetParents(Int32 projectId, Int32 testFolderId, Boolean includeSelf) at APPLICATION.Web.Services.Ajax.TestSetTestCaseService.RetrieveNameDesc(Nullable`1 projectId, Int32 testSetTestCaseId, Nullable`1 displayTypeId) at SyncInvokeRetrieveNameDesc(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet) I tried to fix the problem by rebuilding indexes, but it had no effect. Spirateam version 6.2.0.1 MS SQL Server 2014 Standard (64) Windows Server 2019 Standard edition, 24 GB, processors 6, Intel Xeon 4216 2.1 GHz Mon, 22 Jan 2024 10:03:06 -05002026-05-04T11:56:32-04:00/Support/Forum/spirateam/issues-questions/2895.aspxmessageId=6588David J (adam.sandman+support@inflectra.com) We have added significant performance improvements in test case folder caching in newer versions of Spira, I would upgrade to 7.11 when you get a chance. Also check to make sure that you have no self-nested test case folders, that can cause an infinite loop and timeout. For more assistance, please log a support ticket . Mon, 22 Jan 2024 13:19:44 -05002024-01-22T13:19:44-05:00/Support/Forum/spirateam/issues-questions/2895.aspx#reply6588messageId=6589Svetoslav SARAKINOV (Svetoslav.SARAKINOV@amadeus.com) [TST_TEST_CASE_FOLDER] has been checked for self-nested folders and none were found. Unfortunately our MS SQL Server is 2014 standard and I think we cant upgrade to Spira 7.x? Tue, 23 Jan 2024 08:04:33 -05002024-01-23T08:04:33-05:00/Support/Forum/spirateam/issues-questions/2895.aspx#reply6589messageId=7184jason bevis (bevisjason0405@gmail.com) To isolate which SQL query is causing the delay: Use SQL Server Profiler or Extended Events to capture: Long-running queries Blocking sessions Wait types (look for CXPACKET, LCK_M_, PAGEIOLATCH_) This will help confirm if: A specific stored procedure is taking too long A query is being blocked or scanning a massive result set Escape Road Sat, 19 Apr 2025 01:21:56 -04002025-04-19T01:21:56-04:00/Support/Forum/spirateam/issues-questions/2895.aspx#reply7184messageId=7197Rose Black (rosebl2244@gmail.com) The timeout errors youre encountering suggest that some database queries are taking too long to execute, possibly due to large data volumes or inefficient query paths. Since rebuilding indexes didnt resolve the issue, we recommend checking for: Long-running queries in SQL Server using tools like SQL Profiler or Extended Events. Database maintenance: Ensure regular stats updates and consider query optimization. Resource bottlenecks: Monitor CPU and memory usage to rule out system-level constraints. Application pool recycling settings in IIS might interrupt long operations. Agario Wed, 23 Apr 2025 05:04:10 -04002025-04-23T05:04:10-04:00/Support/Forum/spirateam/issues-questions/2895.aspx#reply7197messageId=7577william john (williamjohn5987son@outlook.com) The timeout on TestCase_RetrieveParentFolders suggests that SQL Server is struggling with a recursive folder lookup that is likely deeper or more data-heavy than the default 30-second execution window allows. Since rebuilding indexes failed, the issue is likely outdated query plans or specific project bloat; you should run EXEC sp_updatestats in SSMS to refresh the optimizer and consider appending ;Command Timeout=120 to the connection string in your Web.config to give the operation more breathing room. Additionally, ensure your SQL Server 2014 is updated to Service Pack 3, as unpatched versions can have threading issues on Windows Server 2019 that lead to these exact types of execution delays. Fri, 20 Mar 2026 12:11:54 -04002026-03-20T12:45:35-04:00/Support/Forum/spirateam/issues-questions/2895.aspx#reply7577