This solution is work for me..

thanks a lot.

I'm having the same problem. i have already set "Connect Timeout=0"... and my query when running in query analyzer takes only 7 secs.. shouldn't that be fast enough? 

 pls help...

thanks..
 

Thanks the command timeout=0 did the trick!

I got the same error executing a complicated stored procedure from my VB.NET application.  However, rather than setting the command timeout = 0 which the documentation said is "not recommended," I just chose a longer interval of time.

MyCmd.CommantType = CommandType.StoredProcedure

MyCmd.CommandTimeout = 300              ' 5 minutes

MyCmd.ExecuteNonQuery

 This solved the problem. 

I am getting the same error too. The CommandTimeout is set to 30, which isn't probably a lot, but all I am doing is updating one record and then inserting 4 new records. It's being done with different SqlCommand and SqlConnection objects, so kinda unrelated. Two statements go one after another and take less then a second in Query Analyzer. What is strange is that if the update/insesrt fails in aplication and I will try exact same statement in Query Analyzer it may take 3-5 minutes to execute (different time every time), but once it's complete, and I try it again it takes less then a second. Also what is strange, it is absolutely inconsistent. It may complete ok one time (or even several) and then next time times out on update or finish update but fails the insert.

Any ideas. Please advise. Thanks.

HI,

I am facing the same problem.

My project is on .Net with SQL Server.

I am trying to retrieve a huge data at a time from DB. Previously it is working fine.

From three days back i am getting  "Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding."

Even i made some changes to solve that

 in web.config i put "connect timeout = 300000" and

     CommandTimeout = 300000     (previously they are 10000)                         // 300000 = 5min

 still i am facing the same problem..

Can any one say solution for this

Regards,

Venkatesh 

I added the code below to the web.config file and it worked.  I found that there are two things that can time out.  The SQL call can time out and the application that is running can time out.

<system.web>
            <customErrors mode="Off"/>
            <httpRuntime appRequestQueueLimit="100" executionTimeout="60000" />
        </system.web>

Hopefully this works!

I am getting this error inside the preview data window when selected from the dataset. How or where to I change the timeout setting?

<add key="DBConnection" value="server=LocalHost;uid=sa;pwd=;database=DataBaseName;Connect Timeout=200; pooling='true'; Max Pool Size=200"/>
 

This is working for me :) thank you.

set the command.connectiontimeout property to maximum integer value

it will solve the problem

'Sample code that has solved a similar problem for me:

Thanks every body the solutions were very helpfull

CmdGenCls.CommandTimeout = 300       worked for me

 Regards

Sara

thanks for your solution on command timeout=0 it works for me :-)