timing problem issue

Hi, I have some kind of timing problem, not sure how to address it yet. I
have a stored procedure that can take from 10 seconds to 2 minutes to return
data to a dataset depending on its input parameters. I have the
da.selectcommand.CommandTimeout = 0 but still when I run it for longer
processing time I get the error object not set to an instance of an object
when I try
document.close method where document is ReportDocument. The data is being
displayed in a Crystal report.
--
Paul G
Software engineer.

Re: timing problem issue

What you are observing is the default timeout for http requests. For 1.1 it
is 90sec and from 2.0 it is 110sec. You can control it with


in web.config file.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net


"Paul" wrote in message
news:B74CBA5D-C18E-4F29-889B-BB81FE9C22EC@microsoft.com...
> Hi, I have some kind of timing problem, not sure how to address it yet. I
> have a stored procedure that can take from 10 seconds to 2 minutes to
> return
> data to a dataset depending on its input parameters. I have the
> da.selectcommand.CommandTimeout = 0 but still when I run it for longer
> processing time I get the error object not set to an instance of an object
> when I try
> document.close method where document is ReportDocument. The data is being
> displayed in a Crystal report.
> --
> Paul G
> Software engineer.

Re: timing problem issue

Thanks for the response. I added
to the web config just under the complitation close tag. It builds without
errors but I am still getting the runtime error like the timeout is not
working, still using default?
The query takes 1:45 to complete so it is greater than the default timeout
for .net 2.0.
--
Paul G
Software engineer.


"Eliyahu Goldin" wrote:

> What you are observing is the default timeout for http requests. For 1.1 it
> is 90sec and from 2.0 it is 110sec. You can control it with
>
> >
> in web.config file.
>
> --
> Eliyahu Goldin,
> Software Developer
> Microsoft MVP [ASP.NET]
> http://msmvps.com/blogs/egoldin
> http://usableasp.net
>
>
> "Paul" wrote in message
> news:B74CBA5D-C18E-4F29-889B-BB81FE9C22EC@microsoft.com...
> > Hi, I have some kind of timing problem, not sure how to address it yet. I
> > have a stored procedure that can take from 10 seconds to 2 minutes to
> > return
> > data to a dataset depending on its input parameters. I have the
> > da.selectcommand.CommandTimeout = 0 but still when I run it for longer
> > processing time I get the error object not set to an instance of an object
> > when I try
> > document.close method where document is ReportDocument. The data is being
> > displayed in a Crystal report.
> > --
> > Paul G
> > Software engineer.
>
>
>

Re: timing problem issue

Also I am not getting the httprequest timeout issue!
--
Paul G
Software engineer.


"Eliyahu Goldin" wrote:

> What you are observing is the default timeout for http requests. For 1.1 it
> is 90sec and from 2.0 it is 110sec. You can control it with
>
> >
> in web.config file.
>
> --
> Eliyahu Goldin,
> Software Developer
> Microsoft MVP [ASP.NET]
> http://msmvps.com/blogs/egoldin
> http://usableasp.net
>
>
> "Paul" wrote in message
> news:B74CBA5D-C18E-4F29-889B-BB81FE9C22EC@microsoft.com...
> > Hi, I have some kind of timing problem, not sure how to address it yet. I
> > have a stored procedure that can take from 10 seconds to 2 minutes to
> > return
> > data to a dataset depending on its input parameters. I have the
> > da.selectcommand.CommandTimeout = 0 but still when I run it for longer
> > processing time I get the error object not set to an instance of an object
> > when I try
> > document.close method where document is ReportDocument. The data is being
> > displayed in a Crystal report.
> > --
> > Paul G
> > Software engineer.
>
>
>