SSRS Error: The timeout period elapsed prior to completion of the operation or the server is not responding

Hi, I am using SQL Server 2008 R2 Stored Procedure as my dataset and running yearly sales report in SSRS 2008 R2. The weird thing is in SSMS the stored procedure does not take more than 10 seconds to retrieve data and the report also works
fine in BIDS, but from ReportServer if I were to pick an year from 1990 - 2014 they all work fine anything prior to 1990 either shows up fine or throws the below error.
SSRS Error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset 'QueryDS'. (rsErrorExecutingCommand)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.
I checked ReportServerTemDb tables and no table seems to be really large to cause a problem. This report "KeepTogether" property is TRUE.
Thanks in advance.............
Ione

Was able to fix this with the help of
msdn documentation. The query dataset was set to 5 and this was somebody else's report I was fixing and I usually have my report template set to 0 so it took me a while to get there.
Ione

Similar Messages

SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Hi,
I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
setup rolls the SCOM install back.
Has anyone seen this issue before or know how to help resolve it?
Appreciate your help, below is the SCOM installation log:
Thanks
Marc
[13:27:27]: Always: :Creating Database: OperationsManagerDW
[13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
[14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :Exception running sql string
DECLARE @sql NVARCHAR(MAX);
SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
    ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
    LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion
of the operation or the server is not responding.
[14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
[14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Always: :InnerException.StackTrace:
[14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or
the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
[14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
marc nalder

Hi,
Based on the log, I recommend you use the following way to test SQL connectivity.
You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
if it fails to connect.
For more information, please review the link below:
The easy way to test SQL connectivity
http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

The timeout period elapsed prior to completion of the operation or the server is not responding

the timeout period elapsed prior to completion of the operation or the server is not responding.
The error shows while executing a (select query) telerik report in MVC.

Hello,
Did you set the CommandTimeOut property of the SQL Command when you call the connection string to SQL Server?
If your select query is complex or the data is larger, please try to specify connectiontimeout property to maximum integer value.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server)

I am getting the error message, "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server)". I am attaching the stored procedure. Can anyone see where the syntax may
be causing this.
USE [ReportData]
GO
/****** Object: StoredProcedure [PDI].[usp_MJTestTop10_Select] Script Date: 04/23/2015 10:35:43 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
--USE [ReportData]
--GO
--/****** Object: StoredProcedure [PDI].[usp_MJTestTop10_Select] Script Date: 04/23/2015 08:22:26 ******/
--SET ANSI_NULLS ON
--GO
--SET QUOTED_IDENTIFIER ON
--GO
ALTER PROCEDURE [PDI].[usp_MJTestTop10_Select]
@StartDate DATE,
@EndDate DATE,
@Location VARCHAR
AS
DECLARE @CalendarKey TABLE (
Calendar_Key int,
Organization_Key int,
Day_Date DATETIME
BEGIN
INSERT INTO @CalendarKey
SELECT C.calendar_key,
O.Organization_Key,
C.Day_Date AS DATETIME
FROM pdi.PDI_Warehouse_952_01.dbo.calendar C,
pdi.PDI_Warehouse_952_01.dbo.Organization O
where @EndDate is not null
and C.Day_Date BETWEEN @StartDate and @EndDate
or @EndDate is null
and C.Day_Date = @StartDate
END
SELECT CAST(C.Day_Date as DATE) as [Memo Date],
--C.calendar_key,
ISNULL(CAST(MBH.Transaction_Number as VARCHAR), 'Unknown') as [Memo Number],
O.Site_id,
O.Site_desc,
--p.Product_Key,
p.UPC as [UPC],
(CAST(P.Department_ID as VARCHAR) + ' ' + CAST(P.Category_ID as VARCHAR) + ' ' + CAST(P.Sub_Category_Id as VARCHAR)) as [D C S],
ISNULL(CAST(IPF.Vendor_Key as VARCHAR), 'Unknown') as [Vendor Code],
--ISNULL(CAST(V.Vendor_Desc as VARCHAR), 'Unknown') as [Vendor Desc],
ISNULL(P.Item_Desc, 'Unknown') as [Description],
ISNULL(P.Size_Desc, 'Unknown') as [Size],
ISNULL(RTrim(Cash.Cashier_Name), 'Unknown') as [Associate],
ISNULL(CONVERT(INT, IIF.Beg_Inv_Qty, 0), '0') as [Old Qty],
ISNULL(CONVERT(INT, IIF.End_Inv_Qty,0), '0') as [Adj Qty],
ISNULL(CONVERT(INT, IIF.End_Inv_Qty - IIF.Beg_Inv_Qty, 0), '0') as [Dif Qty]
FROM pdi.PDI_Warehouse_952_01.dbo.Item_Sales_Fact ISF
INNER JOIN pdi.PDI_Warehouse_952_01.dbo.Product P ON ISF.Product_Key = P.Product_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Organization O ON ISF.Organization_key = O.organization_key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Item_Purchases_Fact IPF ON ISF.Product_key = IPF.Product_Key
AND ISF.Organization_key = IPF.Organization_key
AND ISF.Calendar_key = IPF.Calendar_key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Item_Inventory_Fact IIF ON ISF.Product_Key = IIF.Product_Key
AND IIF.Product_Key = P.Product_Key
AND ISF.Organization_key = IIF.Organization_Key
AND ISF.Calendar_key = IIF.Calendar_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Calendar C ON ISF.calendar_key = C.calendar_key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Cashier Cash ON ISF.Organization_Key = Cash.Organization_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Cashier_Metric_Hourly_Dept_Snapshot CMH on Cash.Organization_Key = CMH.Organization_Key
AND Cash.Cashier_Key = CMH.Cashier_Key
AND ISF.Calendar_Key = CMH.Calendar_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.MarketBasket_Header MBH ON ISF.Calendar_Key = MBH.Calendar_Key
AND ISF.Organization_Key = MBH.Organization_Key
AND Cash.Cashier_Key = MBH.Cashier_Key
LEFT JOIN pdi.PDI_Warehouse_952_01.dbo.Vendor V ON IPF.Vendor_Key = V.Vendor_key
AND IPF.Calendar_Key = C.Calendar_Key
LEFT JOIN @CalendarKey CK ON ISF.Calendar_Key = ck.Calendar_Key
AND ISF.Organization_Key = CK.Organization_Key
WHERE C.calendar_key = CK.Calendar_Key
ORDER BY
O.Location_ID,
C.Day_Date,
IPF.Vendor_Key,
P.UPC,
P.Size_Desc

Some additional comments.
@Location VARCHAR
Look closely at this. How many characters can @Location contain? You did not specify, so perhaps you think some appropriately large default value is used. Guess again. You did a similar thing with cast (multiple times) - which is handled
differently. Don't be lazy.
WHERE C.calendar_key = CK.Calendar_Key
Go review the join to the CK table. It is an outer join. Yet you have included criteria in the where clause that requires a match in the unpreserved (@CalendarKey aka CK) table. This effectively transforms that join from outer to inner.
Was that intentional? Probably, but then you don't need to use an outer join
FROM pdi.PDI_Warehouse_952_01.dbo.calendar C,
pdi.PDI_Warehouse_952_01.dbo.Organization O
Evolve. We do not join in the where clause any longer. You should be joining using join operators. And perhaps more importantly, why do you need to dump a resultset into a table variable at all? Note that your join is a cross join
since there is no relationship between calendar and Organization - intentional? Given the rest of the logic, it seems that you don't really need to do this.
ISNULL(CONVERT(INT, IIF.End_Inv_Qty,0), '0') as [Adj Qty],
Go review the documentation for convert. You supply a style, but does it do anything? We don't know what datatype End_Inv_Qty is, but I assume it is numeric (and not float). So what do you intend? And you convert it to integer but
use a character '0' in the isnull function. Your lack of consistency can lead to issues that are difficult to find and resolve.
CAST(C.Day_Date as DATE)
Why are you doing this? You defined the column in your table variable as datetime. You cast the value you use to populate this column to datetime. I'm guessing that you only really care about the date portion. The name you used for the
column implies this. So why bother with datetime in the first place?
And one last suggestion. If you disallow the use of NULL for the @EndDate argument (simply supply the same value for both date arguments) you can simplify the logic that populates your table variable (or its replacement) and greatly eliminate the confusion
and chance for errors that nullability requires.

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. This failure occured while attempting to connect to the Principle server.

We are using SQL Server 2012.
Every now and then, when we execute the below stored procedure INSERT_INTO_MYTBL, we got the below error, and it returned @ID = 0.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This failure occured while attempting to connect to the Principle server."
What causes this error, and how can we fix it ?
Thank you.
create procedure INSERT_INTO_MYTBL
@ID int output,
@Order varchar(50) = NULL,
@ACCOUNT varchar(20) = NULL
AS
DECLARE @Success int, @TryNr int, @ErrMsg varchar(500), @ErrNumber int, @expected_id int;
SET @Success = 0;
SET @TryNr = 1;
SET @ErrMsg = ''
WHILE @Success = 0 AND @TryNr <= 3 and @ErrMsg = ''
BEGIN;
BEGIN TRY;
BEGIN TRANSACTION;
retry:
BEGIN TRY;
SELECT @expected_id = ident_current('myTbl') + 1
SELECT @order = @account + '-' + CAST(@expected_id AS varchar(50))
insert into myTbl
([Order],ACCOUNT)
values
(@Order,@ACCOUNT)
END TRY
BEGIN CATCH;
SELECT @ErrNumber = ERROR_NUMBER()
IF @ErrNumber = 2627
BEGIN;
GOTO retry
END;
ELSE
BEGIN;
SET @ErrMsg = '1.' + ERROR_MESSAGE() + ' ' + @order
RAISERROR (@ErrMsg, 16, 1);
END;
END CATCH
select @ID = SCOPE_IDENTITY()
IF @id <> @expected_id
BEGIN
UPDATE myTbl
SET [Order] = @ACCOUNT + '-' + CAST(@ID AS varchar(50))
WHERE ID = @ID
END
SET @Success = 1
COMMIT TRANSACTION;
END TRY
BEGIN CATCH;
ROLLBACK TRANSACTION;
SELECT @ErrNumber = ERROR_NUMBER()
IF @ErrNumber = 1205
BEGIN;
SET @TryNr = @TryNr + 1;
IF @TryNr > 3
RAISERROR ('Giving up after 3 consecutive deadlocks for %s', 16, 1,@ACCOUNT);
END;
ELSE
BEGIN;
SET @ErrMsg = '2.' + ERROR_MESSAGE() + ' ' + @order
RAISERROR (@ErrMsg, 16, 1);
END;
END CATCH;
END;

When the problem occurs, the stored procedure returns @ID = 0, which I think means the query
When the problem occurs, the procedure does not return anything. SQL Server was told to stop executing. Furthermore, unless you issue the command SET XACT_ABORT ON, SQL Server will not roll back any open transaction. Which is one more reason you should not
permit command timeouts.
As for why this procedure sometimes take a long time, I would primarily suspect locking. When this occurs (but before the timeout elapses!), you could use my beta_lockinfo to see if there is any blocking going on. You find it here:
http://www.sommarskog.se/sqlutil/beta_lockinfo.html
Erland Sommarskog, SQL Server MVP, [email protected]

Timeout expired. the timeout period elasped prior to completion of the operation or the server is not responding

HI All --- i am facing " Timeout expired. the timeout period elapsed prior to completion of the operation or the server is not responding " facing this issue every second day in our database.. for the rectification we just restart
the DB instance and its start working fine..... although database is in working condition and other databases in same instances are working fine, please suggest me any remedy to get rid from this issue.

Imran,
Check this:
http://sqlserverplanet.com/troubleshooting/fix-timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding
(similar thread)
http://social.msdn.microsoft.com/Forums/silverlight/en-US/685816f3-8d06-4411-8d00-d34c48c2938d/timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is?forum=silverlightgamedev
http://blogs.msdn.com/b/spike/archive/2008/07/31/timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding.aspx
Thanks,
Jay
<If the post was helpful mark as 'Helpful' and if the post answered your query, mark as 'Answered'>

SharePoint - Error_1_Error occurred in deployment step 'Add Solution': Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was rea

Hi,
I am Shanmugavel, SharePoint developer,
I am facing the below SharePoint 2013 deployment issue while deploying using VS2012.
If i will deploy the same wsp or existing wsp
(last build) using direct powershell deployment, the solution adding properly, but the same timeout exception coming while activation the features. Please find the below error.
I tried the below activists:
1. Restarted my dev server, DB server.
2. tried the same solution id different server
3. tried existing wsp file (last build version)
4. Deactivated all the features, including project Active deployment configuration.... but still i am facing the same issue.
I hope this is not coding level issue, because still my code is not start running, before that some problem coming.
Please help me any one..... Last two days i am struck because of this...

What you need to understand is the installation of a WSP does not do much. It just makes sure that you relevant solution files are deployed to the SharePoint farm.
Next comes the point when you activate the features. It is when the code which you have written to "Activate" certain features for your custom solution.
Regarding the error you are getting, it typically means that you have more connections (default is I guess 100) open for a SQL database then you are allowed to.
If you have a custom database and you are opening a connection, make sure you close it as well.
Look at the similar discussion here:
The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool
size was reached[^]
I would suggest further to look at the
ULS logs[^] to get better insight.
Manas Bhardwaj's Stream : www.manasbhardwaj.net

Cloud Database issue:-Timeoutexpired. The Timeout perion elapsed prior to completion of the operation or the server is not responding

I am facing following issue in cloud database
Issue: Altering any stored procedure in cloud database, Application throwing time out issue.
If same stored procedure running in backend(SQL),it’s executing without delay i.e. executing in 3 sec, not sure what is happening.
This is not happening on regular basis, After altering procedure if I wait for 15 to 20 minutes(not running any queries) then it will automatically get resolved.
Please let me know if any fix is available for the above issue.

Hello,
Try to enable TCP/IP and Named Pipes using the following article. Restart SQL Server service when done.
http://technet.microsoft.com/en-us/library/ms191294.aspx
Enable and start SQL Server Browser service.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

What is causing this "The timeout period elapsed during the post-login phase."?

This is happening on a shared environment running DataCenter. We are doing a bulk merge of about 100 plus records. It is failing in different spots but always the same error. Sql has no error logs, and we are not seeing locks.
We need some hints as to what this error message really means.
System.Data.SqlClient.SqlException: Connection Timeout Expired. The timeout period elapsed during the post-login phase.
The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed
out while attempting to create multiple active connections. The duration spent while attempting to connect
to this server was - [Pre-Login] initialization=1; handshake=1; [Login] initialization=0; authentication=0;
[Post-Login] complete=14000; ---> System.ComponentModel.Win32Exception: The wait operation timed out

Well, at first hand, it looks like a "time-out", obviously.
I would check the system's resources, if it's extremely busy at that time at first. Especially CPU.. and general Login statistics
Andreas Wolter | Microsoft Certified Master SQL Server
Blog: www.insidesql.org/blogs/andreaswolter
Web: www.andreas-wolter.com

Error: Device\Ide\iaStor0, did not respond within the timeout period.

Hello,
In last few months, I began getting the error:
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
My system hangs and slows to a crawl. Error seems to be well-known, and solution is to install the latest version of Intel Matrix Manager, which is 8.6. I've done this, I reinstalled my OS, and I've reinitialized my hard Raid1 array. None of this has helped.
http://www.intel.com/support/chipsets/imsm/sb/cs-025783.htm
Any suggestions?
Thx.
Scott

Quote
Have you tested HDD's with Seagate diagnostic utility?
Going by the link you have provided I assume you are using Vista?
Yes, I am using Vista and I did also use Sea Tools; no issue identified. I'd love to hear more suggestions. Things I've done:
1. Reformat / reinstall. Helped, but problem not eliminated.
2. Ran SeaTools Disk Diagnostic. No issue.
3. Installed Intel Matrix STorage, most recent version 8.6. Should've fix prob, but didn't.
4. Upgraded Bios from 7.5 to 7.9.
Seems like the upgrade to Intel Matrix Storage Manager should've fixed this issue, but it didn't. Any particular drive identified in the error message in the original post?
It is also not clear what changed to have introduced this error. My system has been stable for 2 years and from the errors looks like I've had problems for the last 3 months, but they got notably worse in the last 2 weeks. Reformatting / reinstall helped, but didn't eliminate these issues. Any insight would be appreciated.

Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

Hi Everybody,
I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard " This operation
returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
thanks

Hi,
Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
updates. Please post the error or warning report.
Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support.microsoft.com/kb/2784261
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

"Error: 0x800705B4. This operation returned because the timeout period expired"

Hello,
I deployed security updates Mid October 201, however some clients failed to install with the error "0x800705B4 this operation returned because the timeout period expired when installing updates".
Although, i saw an article but this did not address the issue. It was advised i temporarily disable any third party antivirus software and firewall.
Unfortunately, we use SEP antivirus and any attempt to disable it would yanck the clients off the network. Windows Firewall is also disabled on these clients.
Can anyone help urgently?

Hi,
What's the status in Software Center about the updates?
Have you checked SCCM updates logs on the clients?
http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
Please also check the boundary groups associated with DPs have been configured correctly.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Adobe 10 error #1460 - Timeout period expired

We have been having a problem with saving documents since the upgrade to Adobe 10. If the document is not saved fast enough,
we get the timeout period expired error #1460. Is there some way to adjust this timeperiod?

http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5b439fe-1aa9-4823-a3ac-d0be643a5073/query-using-ad-module-timed-out?forum=winserverDS
has some more information on this, though I don't know if there were any improvements to the AD Module in the last year that might change this situation.
Long story short, the AD module is good for small scale, but beyond that, you might be better off using the System.DirectoryServices classes for better performance and finer control.

Controlling the timeout period when synchonizing with cluster

I see a message when my server starts up:
          "Waiting to synchronize with other running members of MyCluster."
          When the other servers in the cluster aren't up, the server waits to time out before continuing with startup (default 30 seconds or so?). Is there a way to control the timeout period?
          Thanks,
          Jim

This can be specified in the console under:
          Environment -> Clusters -> "MyCluster"
          You have to click the "Advanced" link to get access to the advanced cluster settings. The name of the property is: "Member Warmup Timeout".
          If you would like to change it programatically, the relevant MBean attribute is : "ClusterMBean.MemberWarmupTimeSeconds"

A remote server did not respond within timeout period

HI
I have a opened in servlet which is not closed.My servlet uses it for various checks.When a request comes after long time, my servlet tries to make a database call and that time I am getting following error.
java.sql.SQLException:IO Exception A remote host did not respond within the timeout period.
Please guide.
Thanks in advance.

I am using the same connection again.
The db server is up and running and the query fetches hardly any data.
when i stop and restart the servlet, everything becomes normal.

SSRS Error: The timeout period elapsed prior to completion of the operation or the server is not responding

Similar Messages

Maybe you are looking for