"....(-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

Similar Messages

Query timeout expired and Invalid object name

I have a program that processes data (dequeues) and polls about every 2.5 seconds - normally there are several records to process per second - it does this constantly 24/7. The program runs fine at about 100 sites. At 2 sites the following error occurs
about once per day. Typically the table has less than 10 records that get processed ie read then deleted. DataObjects are used ie the data is read, connection closed, processed, deleted using T-SQL from ADO - ie transactions are as short as possible.
Error#-2147217871 Query timeout expired. SQL:SELECT RealID, RxerID, PhoneID, Min(ServerDtTm), min(ID) FROM dbo.tblPreReceiver GROUP BY RealID, RxerID, PhoneID ORDER BY Min(ServerDtTm), min(ID)
Inner exception Error No. -2147217865. Error Desc:Invalid object name 'dbo.tblPreReceiver'.. Native Error:208 Source:Microsoft OLE DB Provider for SQL Server SQL State:42S02.
SQL Server 2008R2 (Express at one site and Standard another).
The program then runs again 2.5 seconds later without error.
Can anyone explain why?
I suspect it is a blocking error but the error message does not suggest this at all. There is another application which writes to this queue, this does not report the error.

Yes, blocking can be the cause. The default command timeout is 30 sec and if the table is locked by an other process, the command waits until the table is accessable ... or the timeout raises. You could increase the timeout value or you could perform "dirty
read" = ignoring lock, but I don't want to suggest to do it.
Olaf Helper
[ Blog] [ Xing] [ MVP]

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 [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]

Unable to access the data from Data Management Gateway: Query timeout expired

Hi,
Since 2-3 days the data refresh is failing on our PowerBI site. I checked below:
1. The gateway is in running status.
2. Data source is also in ready status and test connection worked fine too.
3. Below is the error in System Health -
Failed to refresh the data source. An internal service error has occurred. Retry the operation at a later time. If the problem persists, contact Microsoft support for further assistance.
Error code: 4025
4. Below is the error in Event Viewer.
Unable to access the data from Data Management Gateway: Query timeout expired. Please check 1) whether the data source is available 2) whether the gateway on-premises service is running using Windows Event Logs.
5. This is the correlational id for latest refresh failure
is
f9030dd8-af4c-4225-8674-50ce85a770d0
6.
Refresh History error is –
Errors in the high-level relational engine. The following exception occurred while the managed IDataReader interface was being used: The operation has timed out. Errors in the high-level relational engine. The following exception occurred while the
managed IDataReader interface was being used: Query timeout expired.
Any idea what could have went wrong suddenly, everything was working fine from last 1 month.
Thanks,
Richa

Never mind, figured out there was a lock on SQL table which caused all the problems. Once I released the lock it PowerPivot refresh started working fine.
Thanks.

Webi Reprot - Query timeout expired(35 Mins)

Hi all,
I am getting below error for one of my webi report. The same report query which takes 5 mins to run against SQL SERVER 2008 R2 data base.
Error Message:
Webi - [Microsoft][SQL Server Native Client 10.0]Query timeout expired
Environment details:
BO : XI3.1 SP3 FP 3.3 Edge
OS: Windows 2008 R2 Data Center , 64 Bit
Tomcat :5.5.20
Same report is running successfully in another BOE Server details given below
BO : XI3.1 SP2 Edge
OS: Windows 2007 SP2 , 64 Bit
Tomcat :5.5.20
Please help me .

Do you have the exact same 32bit DSN setup on both servers ?
Using same version of drivers ?
Are they both connecting to same DB ?
If you run tracert from each server to the DB - do you get same result ?
If you run this query in MS SQL studio on each server - you get same results timewise ?

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.

Query timedout expired error while removing PRIV from a Role in IDM

I am trying to remove a PRIV from a role and i am getting Query timeour error.
I tried removing this PRIV from workflow and there it takes some time to process and then i get a promt of error which is staying for a sec and then i get to home page.
I also tried removing this PRIV from Identity center and there I get error window like this:
Method: Save Identity Store Privilege
Source: Microsoft SQL Native Client
Error: 80040E31h (-2147217871)
Description: Query timedout expired.
this is the error i am getting when i try.
This is very critical role assigned to many users.
Please check this and let me know if you need any more information to understand and give a solution.
FYI: I am on SAP Netwearver 7.0 version.
This role is assigned to almost 1150 users in the system.
Since, I dint see anyone giving answer for this, may be this helps to analyse the solution for this.
Edited by: ARUN KUMAR AKUTHOTA on Apr 28, 2010 3:33 PM

Dear Sabita,
Any update if this has been fixed in SP13 or SP14. We are planning to upgrade to SP13.
We are unable to do even provisioning in multiple systems. Only in 1 system role is getting provisioned and other system its not happening. Same situation for removal of roles also.
Also, we have not upgraded the ABAP patches in A2D system to synch with GRC SP9, whereas in R1D the patches are in synch with GRC SP9. But the issue is happening with R1D system (patches are in Synch) and not in A2D system.
Thanks and Best Regards,
Srihari.K

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

Query Timeout on stored procedure executed from Access 2010

I am trying to delete old jobs from a SQL 2008 R2 database. I created a stored procedure on the server that deletes all Jobs over 1 year old. The delete can take several minutes to run as it deletes record on several related tables. I am getting a error
"2147217871 - [Microsoft][ODBC SQL Server Driver]Query timeout expired". The query runs fine on the Server. I have tried setting Client timeout to 300 sec but it times out way before 5 min. I am not sure what else I
can do to fix this problem. I am hoping someone has seen this and figured out a fix.
Here is there code
Public Sub Cleanup_Database()
On Error GoTo CleanUp_Err
    Dim cmd As ADODB.Command
    Set cmd = New ADODB.Command
    ODBC_conn = "ODBC;Description=testbox2;DRIVER=SQL Server;" & _
                "SERVER=O2GMSAPPTEST\SQL122DEVL;Trusted_Connection=Yes;" & _
                "APP=Microsoft Office 2010;DATABASE=IMB_TraceData;StatsLog_On=Yes"
    cmd.ActiveConnection = ODBC_conn
    cmd.CommandType = adCmdStoredProc
    cmd.CommandText = "DataBase_Cleanup"
    cmd.Execute
CleanUp_Err:
    Dim i As Long
    Dim str As String
    str = ""
    For i = 0 To Errors.Count - 1
        str = str & Errors(i).Number & "-" & Errors(i).Description & " " & vbNewLine
    Next i
    If str = "" Then
        str = Err.Number & " - " & Err.Description
    End If
    MsgBox str, , "Trace Update"
End Sub


You didn't say how you were setting the client timeout, but this has worked for me in an adp.
'Temporarily increase query timeout, which is an application-wide setting
'CurrentProject.Connection.CommandTimeout = 60 'Too late to change this setting- no effect
Const cstrTimeoutOptionName As String = "OLE/DDE Timeout (Sec)"
Const clngTimeoutSecondsForQuery As Long = 300
strQueryTimeOutOriginal = Application.GetOption(OptionName:=cstrTimeoutOptionName)
Application.SetOption cstrTimeoutOptionName, CStr(clngTimeoutSecondsForQuery)
Paul

[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?

Out of nowhere, consistant query failures, SQL Azure USA South, Timeout expired. or TransientFailure exceptions..

Getting a bunch of SQL query failures since yesterday morning pacific time. Have not made changes to any code in months, and server load is about same as it has been for a year. Are you guys doing anything to SQL Azure? This is USA South.
This is a 20MB database and I'm doing queries on tables with couple thousand entities, shouldn't fail like this!
Using latest EntityFramework 6.1.1.
Fails at the SQL server no matter where I connect from.
Compiled Linq to Entity queries seem to be failing. The do have some .Includes..
These are the two most common issues:
System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to
completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out
   --- End of inner exception stack trace ---
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.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.SqlDataReader.TryConsumeMetaData()
   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, 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.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.ExecuteReader(CommandBehavior behavior)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.<Reader>b__c(DbCommand t, DbCommandInterceptionContext`1 c)
   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
   at System.Data.Entity.Internal.InterceptableDbCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
   --- End of inner exception stack trace ---
   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
   at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context, ObjectParameterCollection parameterValues)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__6()
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
and
System.Data.Entity.Core.EntityException: An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy. ---> System.Data.Entity.Core.EntityCommandExecutionException:
An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing
connection was forcibly closed by the remote host.) ---> System.ComponentModel.Win32Exception: An existing connection was forcibly closed by the remote host
    --- End of inner exception stack trace ---
    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.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
    at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
    at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
    at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
    at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)
    at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
    at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
    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, 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.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.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
    at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
    at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
    --- End of inner exception stack trace ---
    at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)
    at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context, ObjectParameterCollection parameterValues)
    at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
    at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
    at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
    --- End of inner exception stack trace ---
    at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
    at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
    at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
    at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
    at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
    at System.Data.Entity.Core.Objects.CompiledQuery.ExecuteQuery[TResult](ObjectContext context, Object[] parameterValues)
    at System.Data.Entity.Core.Objects.CompiledQuery.Invoke[TArg0,TArg1,TResult](TArg0 arg0, TArg1 arg1)

Hi，
I’m writing to follow up with you on this post. Was the problem resolved after performing our action plan steps?If you are satisfied with our solution, I’d like to mark this issue as "Answered". That way, other community members could benefit from
your sharing.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

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,

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

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

Similar Messages

Maybe you are looking for