C#.net Console Application SQLCommand.CommandTimeOut property not working

Question

I have a console application written in C# 4.0. I am running a SQL stored procedure that sometimes takes too long and and a connection timeout exception gets thrown.

To handle it, I first set Timeout to 360 in the connection string in the web.config file but no luck.

Then i tried:

SQLCommand cmd = new SQLCommand();
 cmd.CommandTimeout = 360;

but this is also not working.

Any help would be greatly appreciated. I tried to do same with the Entity Framework 4.0 but had the same issue. The timeout value i am providing is not being applied!

<add name="ConnectionString" connectionString="SERVER=db.mydomain.com;DATABASE=DatabaseName;UID=userID;PWD=Password;Connect Timeout=360;Packet Size=8192;Pooling=True;Min Pool Size=1;Max Pool Size=1000;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />

Exception:

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

So, you want a 6-minute timeout, and it's still timing out at the default 30 seconds? — McGarnagle
– McGarnagle, Commented Jun 24, 2012 at 4:04
I think you are getting confused with command.CommandTimeout and connection timeout. In your web config u have specified connect timeout to 360 — praveen
– praveen, Commented Jun 24, 2012 at 4:17
@praveen I see what you are trying to tell me. I am trying both I have added my exception message on top , please take a look — HaBo
– HaBo, Commented Jun 24, 2012 at 4:20
Try removing connection timeout from your web.config file and use only CommandTimeout in your code — praveen
– praveen, Commented Jun 24, 2012 at 4:28

Pankaj · Accepted Answer · 2012-06-24 11:35:43Z

4

Set the CommandTimeout = 0 in your code and remove it from the config file.

Setting the Timeout = 0 means, it will complete the job in case of long operation also.

answered Jun 24, 2012 at 11:35

Pankaj

10.2k40 gold badges152 silver badges298 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Kevin Aenmey · Accepted Answer · 2012-06-24 04:05:15Z

0

Do you have context connection=true in the connection string in your Web.config file? According to MSDN:

CommandTimeout has no effect when the command is executed against a context connection

answered Jun 24, 2012 at 4:05

Kevin Aenmey

13.4k5 gold badges48 silver badges45 bronze badges

2 Comments

HaBo Over a year ago

I have added my coonectionstring, please take a look

Kevin Aenmey Over a year ago

Your connection string looks fine to me so that can't be the problem.

Collectives™ on Stack Overflow

C#.net Console Application SQLCommand.CommandTimeOut property not working

2 Answers 2

Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related