Asp.net 2.0 error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using windws 2003 std edition server with IIS 6.0 which was ruuning fine
with dot net frame work 1.1 with out any errors. But in last week I have
installed dotnet frame work 2.0 which are generating a unique error message
in event viewer. Please find the error message below and help me in resolving
this issue.


Error1 :- Unable to get the private bytes memory limit for the W3WP
process. The ASP.NET cache will be unable to limit its memory use, which may
lead to a process restart. Error: 0x80070005

I appreciate your help in this reagrd.

Thanks
Ravi Chander
 
Hello Ravi,

What behavior leads to this exeption?

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RC> I am using windws 2003 std edition server with IIS 6.0 which was
RC> ruuning fine with dot net frame work 1.1 with out any errors. But in
RC> last week I have installed dotnet frame work 2.0 which are
RC> generating a unique error message in event viewer. Please find the
RC> error message below and help me in resolving this issue.
RC>
RC> Error1 :- Unable to get the private bytes memory limit for the W3WP
RC> process. The ASP.NET cache will be unable to limit its memory use,
RC> which may lead to a process restart. Error: 0x80070005
RC>
RC> I appreciate your help in this reagrd.
RC>
RC> Thanks
RC> Ravi Chander
 
Hi Michael,

Actually my server is running with some asp.net websites , among them few
websites are running on framework 1.1 and few more on framework 2.0. For
every 20-3 mins these errors are generating.

let me know what other information you need on this so i can work out an
dgive you.

Thanks
Ravi Chander
 
Hello Ravi,

Try this:

This error is caused by a known issue with insufficient permissions in your
IIS metabase. The metabase ACL's on the target server did not include the
IIS_WPG group on the following two nodes of the metabase (IIS_WPG is in both
ACL's on a clean install):
- W3SVC/AppPools
- W3SVC/Filters

You can download the MetaACL utility from http://support.microsoft.com/?id=267904.
After you have installed the program, open a command prompt and navigate
to the directory where you installed it. Then type the following:

cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE



---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RC> Unable to get the private bytes memory limit for the W3WP
RC>
RC>> process
RC>>
 
Back
Top