Dataset Timeout expired error in SSRS

I am pulling my hair out over these timeout errors in SSRS.
I am running SSRS 2012 in native mode on a Windows 2012 server. When I try to run and embedded dataset in my report it will continually timeout after 90 seconds no matter what I have the timeouts in the report or on the servers rsreportserver.config
file or the web.config file set to.
If I run Query Designer in the report and run the query all fields and the subset of data is returned without an issue in about 45 seconds. As soon as it tries to update the fields then it times out after 90 seconds.
What else can I check to get this working.
Below is what I am getting each time.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

Hi Ronald,
According to your description, after you update the data in base tables, the error message "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." is thrown out when you run query
designer.
In rsreportserver.config file, the value of “DatabaseQueryTimeout” is passed to the System.Data.SQLClient.SQLCommand.CommandTimeout property. The value specifies the number of seconds after which a connection to the report server database times out. It works
on report server side.
Query time-out values are specified during report authoring when you define an embedded dataset. The time-out value is stored with the report, in the Timeout element of the report definition. So in your scenario, you should set the value of Time out in Dataset
Properties. Please refer to the screenshot below:
Reference:
Setting Time-out Values for Report and Shared Dataset Processing (SSRS).
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu

Similar Messages

Timeout expired error when inserting into a mirrored server

We have 3 SQL Server 2012 servers.
All 3 SQL Server has the same database, ie myDB.
In 2 of the servers (say server A and B), myDB is mirrored, and on the 3rd server myDb is NOT mirrored.
When the program calls a stored procedure to insert a record into a table in the database, on the mirrored servers (server A and B) sometimes it takes up to 7 seconds and gave an error "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." This doesn't happen all the time, but happens often enough throughout the day.
The 3rd server (that is NOT mirrored) never gives this Timout expired error.
Will mirrored server cause slowness in writing, thus causes the Timeout expired error ?
Thank you.

Since we can live with some missing data, I think we should use asynchronous mirroring instead of synchronous, do you agree ?
That may be an options, provided that you are on Enterprise Edition. As I recall, Standard Edition only has synchronhous mirroring.
There are caveats with asynchronous mirroring. One is data loss in case of a failover, which you say that you can live with. There may be more caveats, though. Unfortunately, since my role is more of a developer than a DBA, I'm not too well versed in
the details. Maybe someone else can fill in?
Can a firewall issue cause mirror latency, that in turn causes the delay in writing to the principal database ?
Firewalls and other network hiccups certainly can cause a latency.
Erland Sommarskog, SQL Server MVP, [email protected]

Changed Database Service Tier resulted in lots of "Timeout-expired-errors"

Last night I changed database service tier from Web Edition to Standard S0. Since then we are getting a lot of errors like this:
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
Before the change we had no such errors. I have tried to make a new deployment of our cloud services but it doesn't change anything. It still fill the error logs with timeout-expired-errors and the site itself seems to be significantly slower than before.
What's the problem? I assume the Standard S0 service tier should be sufficient in performance. We don't have much traffic on the site.
Hope someone can shed a light...

Folks we know that changing business models is a hard thing to do. In the Web/Business case, you pay on size of the DB and you get whatever performance we have at the time. Sometimes this is great, other times this is ok and sometimes performance
is very poor. Customers have given us feedback that this unpredictable performance is very difficult to deal with.
Using this feedback as a key input, the business model for Basic/Standard/Premium is $/perf. As Jan points out below, understanding what resources your consuming is a great first step before moving to B/S/P.
Your mileage may vary here. Many customers see a decrease because of this business model change. Others see no impact, and some will see an increase if their DBs are very small and consume a lot of resources.
Jan, I and the team would be happy to help customers move into the new business model. To have great conversations will need some customer specifics that aren't best shared in a public forum. guyhay@microsoft is my email if you'd like to have
that conversation.

"....(-2147217871) Query timeout expired" -- Error in MS Dynamics RMS HQ Manager

When I go into the reports section of HQ Manager, then Quotes/Orders to search a purchase
order, once I start the search it times out with an error,
“The report data could not be loaded due to the following error (-2147217871) Query timeout
expired”
Is this due to .NET 30 second default timeout?
Thanks in advance - Roxy

How is this SSIS related?
Arthur
MyBlog
Twitter

[Macromedia][Oracle JDBC Driver]Execution timeout expired

From time to time, I get "[Macromedia][Oracle JDBC Driver]Execution timeout expired" errors in my log files on queries that should normally take < 10 ms. If this happens too often (the exact count seems to be different every time), ColdFusion stops responding (and logging!).
Between CF and the Oracle DB server I have a firewall.
The firewall seems to be ok, Oracle stops receiving db requests without further errors and CF stops without writing anything in the log files.
What now? I'm using the latest CF9, fully patched and updated. We use a reboot script for the time beeing, but we'd like to know what is going on.

Is there any way you can bypass the firewall on a networking level to rule it out?

Powerpivot Report 2010 - OLE DB or ODBC error: Query timeout expired; HYT00

0
I have report already developed by someone in powerpivot 2010 and deployed to sharepoint in powerpivot gallery library. The data source for this report is SQL Server 2008 r2. I have set the refresh options in sharepoint to run after business hours during
week end. When I check the refresh history it shows this error message "OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the
transaction failed..
I have tried to run the "Also refresh as soon as possible " just to check but same error message is shown.
This is the detailed error message details:
03/02/2014 21:06:55 03/02/2014 22:08:15 01:01:20 Failed
OLE DB or ODBC error: Query timeout expired; HYT00. An error occurred while processing the 'xxx' table. The current operation was cancelled because another operation in the transaction failed
Could anyone guide me on this issue? Truly appreciate your help in advance.

Hi asritha,
I would suggest you take a look at the following articles regarding how to configure PowerPivot data refresh in SharePoint Server:
Configure and Use Stored Credentials for PowerPivot Data Refresh:
http://technet.microsoft.com/en-us/library/ee210671(v=sql.105).aspx
Configure and Use the PowerPivot Unattended Data Refresh Account:
http://technet.microsoft.com/en-us/library/ff773327(v=sql.105).aspx
Note: Please ensure that the account have sufficient permission access to your data source.
In addition, please elaborate your PowerPivot data soure with more detail. If you are using SSAS cube, please try to increase "ExternalConnectionTimeout" property default value to see if this helps. Here is the similar thread for your reference,
please see:
http://social.technet.microsoft.com/Forums/en-US/35b26c06-9e6d-41e5-ae44-bfb1233510ac/ssas2008-ole-db-error-ole-db-or-odbc-error-query-timeout-expired-hyt00?forum=sqldatamining
Regards,
Elvis Long
TechNet Community Support

Error occured in deployment step 'Activate Features': Timeout Expired

Hi all,
Today when I deploy SharePoint 2010 application using visual studio I faced the error.
"Error
18
Error occurred in deployment step 'Activate Features': 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 reached."
How to solve this
s.vijay

one of the possible thing is may be their is SQL connection leak in your code.You can trace it using sql profile...check this post for more details:
http://social.technet.microsoft.com/Forums/en-US/7134eb37-621a-4be1-93b2-0f53ac2d912f/error-occurred-in-deployment-step-add-solution-timeout-expired?forum=sharepointgeneralprevious
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

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.

Error [hyt00] [microsoft][odbc sql server driver] query timeout expired

I have the below network setup:-
1. Its a simple network at my father's office at a small town called Ichalkaranji (District - Kolhapur, Maharashtra).
2. We are using private network range 192.168.1.xxx with two Windows Server 2003 Enterprise Edition with SP2 licensed copies and 15 local Windows 7 clients who are only using Server A.
3. The network is having a TP-Link Braodband Router Connected to internet with the IP 192.168.1.1.
4. Both there Windows Server 2003 Enterprise Edition with SP2 are running separate SQL Server 2005 Express with Advanced Services, you can treat them as Server A (Problematic Server with IP of 192.168.1.2)
and Server B (this is not having any issue with IP of 192.168.1.3).
5. Server A is also being used by 6 Remote users from our Kolkata office using DDNS facility through the NO IP client software which installed separately on both the servers. Kolkata remote users
do not use OR access the Server B.
6. Server B is being used by only 2 Remote users from our Erode office (Under Salem District, Tamilnadu) using DDNS facility through the NO IP client software which installed separately on both
the servers. Erode remote users do not use OR access the Server A.
7. The front end application which running separately on both the servers have been developed in VB by a local vendor at Ichalkaranji (District - Kolhapur, Maharashtra).
8. Both Servers are having the same database structure in terms of design and tables format. Only difference is that both the servers are being used separately.
9. This error OR problem is only related to Server A, where on the clients we get the message "error [hyt00] [microsoft][odbc sql server driver] query timeout expired" every now and then.
10. We have to frequently reboot the server whenever we get this message on the client machines. May be after rebooting every thing works perfectly for 2 hours / 5 Hours / may be one full day but
the the error will come back for sure.
11. Current Database back up size on Server A is around 35 GB and take around 1 hour 15 minutes daily to take the back up.
12. Current Database back up size on Server B is around 3 GB and take around 5 to 10 minutes daily to take the back up.
13. One thing I have noticed is that when ever we reboot Server A, for some time sqlsrvr.exe file will show memory usage of 200 to 300 MBs but it will start using slowly, what i understand is that
this is the way SQL Server works.
14. Both the Servers are also running Quick heal Antivirus Server Edition separate licensed copies also.
15. Server B is also running Tally ERP 9 Licenses copy which is being used locally by 15 users of Ichalkaranji (District - Kolhapur, Maharashtra) same users
Can any one help to resolve this issue. Any help will be highly appreciated.

The error message "query timeout expired" occurs, because by default many APIs, including ODBC only waits for 30 seconds for SQL Server to send any output. If no data has been seen for this period of time, they tell SQL Server to cancel execution
and return this error to the caller.
This timeout could be seen as a token that the query is taking too long time to execute and this needs to be fixed. But it can also be a pain in the rear parts, if you are content with a report taking five minutes, because you only run it once a day.
The simplest way to get rid of the error is to set the timeout to zero, which means "wait forever". This is something your vendor would have to do. This may, however, not resolve the problem, as the users may just find that the application is hanging.
To wit, there are two reasons why the query takes more than 30 seconds to complete. One is that there is simply that much work to do. This can be reduced by adding indexes or by doing other tuning, if the execution time is not acceptable. The other possibility
is blocking. That is, there is a process blocking this query from completing. This is much more likely to require attention.
It is not clear to me, whether the vendor has developed the database part as well. In this case, you should probably call the vendor's support desk to have them to sort this out.
Finally, I am little puzzled. You say that you are using Express Edition, but one of the databases is 35 GB in size. 35 GB is far above the limit for Express Edition.
Erland Sommarskog, SQL Server MVP, [email protected]

2008 r2 Copy Database Wizard Error code 0x80004005 (login timeout expired).

While on copy database wizard, step Configure the package I
get this error:
while trying to find a folder on sql an ole db error was encountered with error code 0x80004005 (login timeout expired).
If I try to run it any way, I got the following in the Execute stage:
the job failed. check the event log on the destination server for details
In the destination server, job history:
Message
Executed as user: WORKGROUP\servername$. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1
for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:26:57 PM Could not load package "package name omitted" because of error 0xC0014062. Description: The LoadFromSQLServer method
has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed. Source: Started: 3:26:57 PM Finished: 3:27:44 PM Elapsed: 47.83 seconds. The package could
not be loaded. The step failed.
I check the job permission with the integration service connection. try with default and with db_ssisadmin.
other info:
Source: Other SQL Server Version, Microsoft SQL Server Enterprise Edition , Build 1617, Microsoft Windows NT 6.0 (6002) NT INTEL X86
Destination: Other SQL Server Version, Microsoft SQL Server Data Center Edition (64-bit) , Build 1600, Microsoft Windows NT 6.1 (7601) NT
x64 Using SMO online transfer

Hi kexinger,
This issue might be caused by the insufficient permission for the SQL Agent account, please check the SQL Agent service account has sufficient permissions to the various folders. For detail information, please take a look at the following article:
http://mattsql.wordpress.com/2014/01/06/quick-tip-could-not-load-package-xxx-because-of-error-0xc0014062/
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

The adapter "SQL" raised an error message. Details "Login timeout expired".

Hi All
Please help me to understand "Login timeout". All feedback is welcome.
BizTalk Server 2009 on Windows Server 2008 R2 64 bit
SQL Server 2008 SP1 64 bit
BizTalk Adapter Pack 2.0
Event Viewer -> Windows Logs -> Application
The adapter "SQL" raised an error message. Details "Login timeout expired".
The adapter failed to transmit message going to send port "ALL.Exceptions" with URL "SQL://xxxxxxxxx/EsbExceptionDb/". It will be retransmitted after the retry interval specified for this Send Port. Details:"Login timeout expired".
Regards
Steve

Hi Abhishek,
Thank you for your input.
I found errors in the Table [EsbExceptionDb].[dbo].[Fault] relating to the write to the target Oracle database
Microsoft.ServiceModel.Channels.Common.MetadataException: Metadata resolution failed for OperationId:ATHENA/Table/WO_ADDITIONAL/Delete ---> System.TimeoutException: Timeout Expired at
The BizTalk send port timeout has been increased from 1 minute to 30 minute and all is well
Regards
Steve

Error -1073807339 Hex 0xBFFF0015 Timeout expired before operation completed

Hi,
I am getting the Error -1073807339 Hex 0xBFFF0015 Timeout expired before operation completed message box but unlike many users that seemed to have a similar problem, it doesn't happened systematically... I am getting the message box error at random on a measurement and then it just works back fine, until the next time it happens again during a continuous measurement acquisiton.
I am working with a HP 34970A, plugged to the pc with a Agilent 82357A USB to GPIB and LabVIEW 2012 sp1. MAX is up to date, so is the I/0 Libraries of Keysight. Drivers are all installed and updated, Communication with IEEE 488 is enable in the I/0 Libraries, passport tullip also in NI VISA through MAX. I run a small VI that should make a continuous acquisition of four temperature using PT strobes plugged to the HP 34970A and graph them, also writting them on a Excel like document. The waiting time between two measurement is set at first by users. To take the measurment, I am runing an adaptated VI from the HP 34970A drivers. I think the problem comes from my VI's structures but I can't find it myself. I am also very surprised that it actually does work fine most of the time and just randomly crash in a loop...
I attached the VIs if needed.
I hope I was clear enough and that you might have an idea to help me fix this problem.
Thank you in advance.
Attachments:
Main_VI.vi ‏17 KB
Agilent 34970 Temp Scan.vi ‏36 KB

Is there someone here to help me?

Critical Error: Cannot Connect to SQL Server. {SQL Server} not found. Timeout expired.

Greetings,
I have been having some issues with various areas in a SharePoint 2013 farm. While working my way through a bazillion errors in the event logs, I have found the following error. It looks to be happening every hour; almost exactly 5 minutes after
every hour.
"Cannot connect to SQL Server. A_PROD_SP01 not found. Additional error information from SQL Server is included below.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
I also find, a health analyzer rule that is failing at the same time:
Availability: One or more servers is not responding.
However, there isn't any server listed in the Failing Servers section.
Any thoughts?
Thank you,
Bob

Hi Bob,
For your issue, it can be caused by that the SharePoint database access account might not have the necessary permissions to communicate with the SQL Server. Please grant correct permissions to the database access account:
You must be a member of the Farm Administrators group to perform this task.
Assign the database access account:
On the Central Administration home page, click Security and in the
General Security section click Configure service accounts.
On the Service Accounts page, in the Credential Management section, in the upper drop-down list click the correct Web application pool for your Web application.
In the Select an account for this component drop-down list, click the domain account that you want to associate with this Web application pool, or click
Register new managed account to associate a new domain account with this application pool.
Click OK to save changes.
Reference:
https://technet.microsoft.com/en-in/library/ee513066(v=office.14).aspx
http://blogs.technet.com/b/wbaer/archive/2009/10/06/intermittent-database-server-connectivity-and-microsoft-sharepoint-products-and-technologies.aspx
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Error: Timeout expired while creating the FDM application

Hi Gurus,
While creating FDM application receiving error "Timeout expired LINE=CREATE DATABASE[Database Name]"
I have provided the db user with db_creator and bulkinsert roles.
Foundation services and Financial Reporting are in the same server and works fine.
Using SQL Server 2005.
FDM Server is in workgroup and SQL server is in domain.
Any ideas....
Thanks,
Edited by: user13024758 on May 27, 2010 7:22 AM

Hello,
While creating a UDL does test the connectivity between the machines it doesn't test permissions or performance.
Keep in mind FDM simple executed an ODBC connection to the server and executed a single SQL Statement. The statement should not take that long to return.
I would percieve that if you take FDM out of the equation and maybe do some wireshark tracing or network review you would find more useful information relating to "timeouts."
How many hops and latency between the two machines if you do a traceroute (tracert)?
Any firewalls between the two that would prohibit "return traffic"?
Are they on the same subnet/lan/router?
What happens if you try another SQL Server box?
Have you installed WireShark on the FDM box and on the SQL Box? If FDM submits the query (which I suspect you would see) does SQL Server try and and return a response code? If so ... does the FDM Server receive the response code?
Keep in mind "other products" don't connect to the database in the same fashion and are not 100% valid comparisons.
Thank you,

Dataset Timeout

Hi,
often I'm not able to save Dataset in BIPublisher and an error of Timeout is shown. There is some parameters that can I change?
I'm on BIPublisher 11g and the source is the OBIEE.
Any Idea?
Regards,
Daniele

Hi Ronald,
According to your description, after you update the data in base tables, the error message "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." is thrown out when you run query
designer.
In rsreportserver.config file, the value of “DatabaseQueryTimeout” is passed to the System.Data.SQLClient.SQLCommand.CommandTimeout property. The value specifies the number of seconds after which a connection to the report server database times out. It works
on report server side.
Query time-out values are specified during report authoring when you define an embedded dataset. The time-out value is stored with the report, in the Timeout element of the report definition. So in your scenario, you should set the value of Time out in Dataset
Properties. Please refer to the screenshot below:
Reference:
Setting Time-out Values for Report and Shared Dataset Processing (SSRS).
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu

Dataset Timeout expired error in SSRS

Similar Messages

Maybe you are looking for