Command Timed Out for Strongly Typed DataSet

Question

4.00/5 (2 votes)

See more:

Hi All,

I have a RDLC report in ASP.Net and to bind that report we are using Strongly Typed DataSet. We are getting Timed Out Expired Exception when we bind the report. We have also checked the Store Procedure on production server that takes approx 5 sec. But when we try to run from production website it throws TimedOut Expired Exception.

We check this with SQL Profiler. When we call the SP from code it execute the SP for 30 sec and throw us the Timed Out Exception. We also tried setting the CommandTimeout Property within the Table Adapter.

C#

((global::System.Data.SqlClient.SqlCommand)(this.CommandCollection[i])).CommandTimeout = 120;

But still it's not working. Our SP is containing table variable, Function, PIVOT, Group BY, SUM

Regards,
Vinod D.

Posted 18-Aug-11 21:00pm

vinod deo from navi mumbai

Updated 18-Aug-11 21:04pm

Prerak Patel

v2

Add a Solution

Comments

Prerak Patel 19-Aug-11 3:06am

Why do you repost it then? Format it properly. BTW, I am deleting your previous question.

Prerak Patel 19-Aug-11 3:07am

and don't shout for downvotes. It was just one vote.

Herman<T>.Instance 19-Aug-11 3:19am

have you done a debug and checked the CommandTimeOut value = 120?
whu u use the CommandCollection?
I my code i use sqlcommand.CommandTimeOut = 14400; and that works.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dirk C De Winnaar · Answer 1 · 2011-09-06T07:43:00

Solution 2

Check this out....

http://blogs.msdn.com/b/angelsb/archive/2004/08/25/220333.aspx[^]

Posted 6-Sep-11 7:43am

Dirk C De Winnaar