Possible Memory Limits with Classic ASP on IIS6?

Morning All,
I am moving a Classic ASP app from Win2000 IIS5 to 2003 IIS6. I have no
problems in IIS5, only in 6. I have researched all possible worker process
recycle problems, as well as the processModel in Machine.Config and found no
reason for an issue. I also cannot run in isolation mode as production will
not allow. The issue is as follows:

* A page contains two ADO record Sets. Each is populated and all rows
placed into its own array with GetRows().

* When one of the recordset objects grows large to a particular number of
rows (in my case apx 2400) and placed into an array, the other array is
dropping its values when I attempt to reference them in the script. When the
first record set/array is below this 2400 threshold, no problems at all with
the other array. All data is available without problem on smaller arrays.

Does anyone have any ideas what IIS or W2K3 settings I can look into to
determine the root cause? It must be a ceiling somewhere I'm hitting that
I'm unaware exists.

Thanks in Advance...Jason

"JasonRhinehart" <JasonRhinehart RemoveThis @discussions.microsoft.com> wrote in message
news:00B6690B-D6AA-43F5-A01C-DCF7AC062845@microsoft.com...
> Morning All,
> I am moving a Classic ASP app from Win2000 IIS5 to 2003 IIS6. I have no
> problems in IIS5, only in 6. I have researched all possible worker
process
> recycle problems, as well as the processModel in Machine.Config and found
no
> reason for an issue. I also cannot run in isolation mode as production
will
> not allow. The issue is as follows:
>
> * A page contains two ADO record Sets. Each is populated and all rows
> placed into its own array with GetRows().
>
> * When one of the recordset objects grows large to a particular number of
> rows (in my case apx 2400) and placed into an array, the other array is
> dropping its values when I attempt to reference them in the script. When
the
> first record set/array is below this 2400 threshold, no problems at all
with
> the other array. All data is available without problem on smaller arrays.
>
> Does anyone have any ideas what IIS or W2K3 settings I can look into to
> determine the root cause? It must be a ceiling somewhere I'm hitting that
> I'm unaware exists.
>
> Thanks in Advance...Jason

I think you're going to need to show us some code that exhibits this
problem.

Also how it is that you are determining the values are going missing from
the array.

I know of no such limits that would silently corrupt an array.