The memory it is referring to is the Process Virtual Memory. Every process
in Windows gets 2GB of memory to use (regardless of RAM installed).
Occasionally, this memory will fragment (just like a HDD will fragment over
time). Unfortunately, unlike a file, memory allocations must be made from
contiguous memory. So, it is possible to have a lot of memory available but
have it all broken up across the memory map.
The biggest cause of problems like this are small memory leaks (on the
orders of 4-8 bytes per leak event). You can 'see' the fragmentation by
using Perfmon and watching Process:PrivateBytes and Process:Virtual Memory
Allocated. The curves should run in parallel. If they divurge (and this
can take a while), then you are fragmenting (i.e. you require more VM to
back proportionately fewer Private Bytes).
Debugging this is not a trivial exercise. Because the memory leaked is so
small, it can be very difficult to identify.
I generally recommend that you start by making sure that you have the latest
binaries (MDAC (www.microsoft.com/data), script engines
(msdn.microsoft.com/scripting) and OS Service Pack). If the problem
persists, move any COM objects you are calling into their own COM+ server
package and see if you can identify the culprit (it will be in the failing
package).
Finally, you can also just restart the specific process that is having the
issue. This recycling is what IIS6 can do automatically and there are other
packages available for IIS5 and previous. No reboot is required.
Pat
"Rajiv" <rajiv_tarafdar RemoveThis @bat.com> wrote in message
news:051f01c37053$dbc40900$a301280a@phx.gbl...
> Hi,
>
> I have suddenly started getting this error for a
> particular application on the IIS Server. (Only
> Transaction site on the box, others are static sites)
>
> Error: File xxxx Line 0 out of memory. Unable to allocate
> required memory..
>
> I think this has to do something with the memory. I put
> perform Monitors and checked the page Faults. Its around
> 500Pages / sec and the Min available bytes is 5000. Can't
> figure out the exact reason.
>
> Any help is much appreciated and Thanks for reading my
> issue.
>
> Regards
> Rajiv<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: IIS Memory Error