IIS not returning data

[Chad]

Got a very strange IIS 5.0 sp3 problem. Basically after
a restart, everything works as expect. We have a very
large report that will return enough data to the client
that the IE process will increase to over 300 meg in
memory. Again this is not a problem after the IIS server
is restarted. The problem we run into is after the IIS
box has been up for a few weeks, and we attempt to run
this report, the report never completes. I can run a
trace on the SQL server and see all of the transaction
completing - including some audit updates we put in the
asp code to track page performance - but the server never
returns data to the client. As a mater of fact, we have
ran network traces between the IIS and the client and it
never sends a packet - other than the ping I was using to
make sure the network trace was workiing. The IIS server
has no pages in queue and reports no errors in the log or
event viewer. Is there something that I am missing? Is
there some sort of problem with large data sets I should
be aware of?


Thanks in advance,

Chad

[Frogbèrt]

I've seen this behaviour before with a machine that leaked memory.
Eventually, the system would hit a certain point (arbitrary) of memory usage
and would simply stop processing the query without any error messages. Check
your code for dirty object handling. You say the IE process takes 300Mb, but
what about Inetinfo and DLLHost on the server?

Robert

"Chad" <chade@jdbyrider.com> wrote in message
news:030801c36e7a$4811d6e0$a501280a@phx.gbl...

> Got a very strange IIS 5.0 sp3 problem. Basically after
> a restart, everything works as expect. We have a very
> large report that will return enough data to the client
> that the IE process will increase to over 300 meg in
> memory. Again this is not a problem after the IIS server
> is restarted. The problem we run into is after the IIS
> box has been up for a few weeks, and we attempt to run
> this report, the report never completes. I can run a
> trace on the SQL server and see all of the transaction
> completing - including some audit updates we put in the
> asp code to track page performance - but the server never
> returns data to the client. As a mater of fact, we have
> ran network traces between the IIS and the client and it
> never sends a packet - other than the ping I was using to
> make sure the network trace was workiing. The IIS server
> has no pages in queue and reports no errors in the log or
> event viewer. Is there something that I am missing? Is
> there some sort of problem with large data sets I should
> be aware of?
>
>
> Thanks in advance,
>
> Chad

[Chad]

Thank you both for your posts. I am not a programmer so
I will have to check with the devel staff regrading their
connections as well as look at the iis and dllhost
processs to see what their memory utilization is. I will
post more information when I have it. Thank you for your
help

Chad

>-----Original Message-----
>Got a very strange IIS 5.0 sp3 problem. Basically after
>a restart, everything works as expect. We have a very
>large report that will return enough data to the client
>that the IE process will increase to over 300 meg in
>memory. Again this is not a problem after the IIS

server

>is restarted. The problem we run into is after the IIS
>box has been up for a few weeks, and we attempt to run
>this report, the report never completes. I can run a
>trace on the SQL server and see all of the transaction
>completing - including some audit updates we put in the
>asp code to track page performance - but the server

never

>returns data to the client. As a mater of fact, we have
>ran network traces between the IIS and the client and it
>never sends a packet - other than the ping I was using

to

>make sure the network trace was workiing. The IIS

server

>has no pages in queue and reports no errors in the log

or

>event viewer. Is there something that I am missing? Is
>there some sort of problem with large data sets I should
>be aware of?
>
>
>Thanks in advance,
>
>Chad
>.
>