Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We run several ASP.NET applications on our webfarm, but we noticed a lot of error entry in the event log:

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.

We stores the web site files on a network share and the application pools running under the "Network Service" account. We did every recommended step (but the problem still appears):

  • aspnet_regiis –ga “Network Service”
  • cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE
  • Add “Connect As” account to IIS_WPG group.
  • Allow "Connect As" accont to logon as a service.
share|improve this question

2 Answers 2

Another possibility if you moved this service or deprecated a domain or something along those lines is that the nominal IIS_WPG permissions assigned to your metabase are for an outdated SID.

To find out what permissions are actually assigned:

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

If IIS_WPG is not listed but a SID is, run the following to add IIS_WPG:

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

The U (unsecured properties read) should be enough for this purpose.

share|improve this answer

Did you restart the IIS service after having executed the scripts? This blog post also recommends using this statement for granting permissions to the filters:

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

This error is caused by a known issue with insufficient permissions in your IIS metabase.

share|improve this answer
    
Yes, we restarted the IIS service... –  user12974 Jul 15 '09 at 11:25

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.