<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. when opening TESTING &gt; TEST SETS v.4.1.0.2 (Thread)</title><description>&#xD;
Hi Guys,&#xD;
&#xD;
    Please can someone help me... I have just finished upgrading SpiraTeam v4.0.0.16 to v4.1.0.2 and the the entire upgrade when smooth with no exceptions... I have now logged into Spirateam and all seems to be fine apart from one thing... When I select TESTING and then TEST SETS i am getting the following error :      System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.        Does anyone know what I can do you fix this ?        Kind Regards     Tyrone </description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spiratest/issues-questions/831.aspx</link><item><guid isPermaLink="false">threadId=831</guid><author>Tyrone R France (tyrone.france@mirada.tv)</author><category domain="http://www.inflectra.com/kronodesk/thread/tag">timeout</category><title>System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. when opening TESTING &gt; TEST SETS v.4.1.0.2</title><description>&#xD;
Hi Guys,&#xD;
&#xD;
    Please can someone help me... I have just finished upgrading SpiraTeam v4.0.0.16 to v4.1.0.2 and the the entire upgrade when smooth with no exceptions... I have now logged into Spirateam and all seems to be fine apart from one thing... When I select TESTING and then TEST SETS i am getting the following error :      System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.        Does anyone know what I can do you fix this ?        Kind Regards     Tyrone </description><pubDate>Thu, 13 Feb 2014 15:04:01 -0500</pubDate><a10:updated>2014-07-23T20:40:48-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/831.aspx</link></item><item><guid isPermaLink="false">messageId=1515</guid><author>Tyrone R France (tyrone.france@mirada.tv)</author><title>&#xD;
This is the Error log within the Admin Panel.&#xD;
&#xD;
        Timeout expired. The timeout period elaps</title><description>&#xD;
This is the Error log within the Admin Panel.&#xD;
&#xD;
        Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.  at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) at Inflectra.SpiraTest.Business.DataAccess.Fill(DataSet dataSet, String srcTable) at Inflectra.SpiraTest.Business.TestSet.Retrieve(Int32 userId, Int32 projectId, Int32 startRow, Int32 numberOfRows, Hashtable filters, Double utcOffset, Nullable`1 releaseId, Boolean includeExecutionData, Boolean includeDeleted) at Inflectra.SpiraTest.Web.Services.Ajax.TestSetService.HierarchicalList_Retrieve(Int32 projectId, JsonDictionaryOfStrings standardFilters, Boolean updatedRecordsOnly) at SyncInvokeHierarchicalList_Retrieve(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs) at Inflectra.SpiraTest.Web.Services.Utils.LocalizationOperationInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs) at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc&amp; rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet) </description><pubDate>Thu, 13 Feb 2014 15:07:10 -0500</pubDate><a10:updated>2014-02-13T15:07:10-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/831.aspx#reply1515</link></item><item><guid isPermaLink="false">messageId=1550</guid><author>Patrik Grill (patrik.grill@juliusbaer.com)</author><title> &#xD;
&#xD;
&#xD;
Hello all together,  we are facing exactly the same issue - we migrated from 3.1 to 4.1.0.2 a</title><description> &#xD;
&#xD;
&#xD;
Hello all together,  we are facing exactly the same issue - we migrated from 3.1 to 4.1.0.2 and also get the error message if we go to the testset view!  Any ideas ?  Thanks in advance and best regards,  Patrik </description><pubDate>Wed, 26 Feb 2014 08:53:31 -0500</pubDate><a10:updated>2014-02-26T08:53:31-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/831.aspx#reply1550</link></item><item><guid isPermaLink="false">messageId=1551</guid><author>Patrik Grill (patrik.grill@juliusbaer.com)</author><title> &#xD;
&#xD;
&#xD;
we also tried to execute the rebuild index script ( http://inflectra.com/Support/KnowledgeBas</title><description> &#xD;
&#xD;
&#xD;
we also tried to execute the rebuild index script ( http://inflectra.com/Support/KnowledgeBase/KB10.aspx ) but it has no effect - we still receive the error message! (we alse have restarted the IIS and DB server) </description><pubDate>Wed, 26 Feb 2014 08:57:14 -0500</pubDate><a10:updated>2014-02-26T08:57:14-05:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/831.aspx#reply1551</link></item><item><guid isPermaLink="false">messageId=1737</guid><author>Andrew Shotton (andrew.shotton@mindgeek.com)</author><title>&#xD;
Did you ever find a solution to your issue? We are having a similar problem with our Spira Test co</title><description>&#xD;
Did you ever find a solution to your issue? We are having a similar problem with our Spira Test configuration.&#xD;
&#xD;
</description><pubDate>Tue, 15 Jul 2014 18:37:42 -0400</pubDate><a10:updated>2014-07-15T18:37:42-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/831.aspx#reply1737</link></item><item><guid isPermaLink="false">messageId=1746</guid><author>David J (adam.sandman+support@inflectra.com)</author><title> &#xD;
&#xD;
&#xD;
There was a specific issue with v4.1.0.2 that was fixed a while back, if you're running the m</title><description> &#xD;
&#xD;
&#xD;
There was a specific issue with v4.1.0.2 that was fixed a while back, if you're running the most recent version (v4.1.0.6) and getting an error, please log a help desk ticket with us.  Regards  Adam </description><pubDate>Wed, 23 Jul 2014 20:40:48 -0400</pubDate><a10:updated>2014-07-23T20:40:48-04:00</a10:updated><link>/Support/Forum/spiratest/issues-questions/831.aspx#reply1746</link></item></channel></rss>