Unable to get the private bytes memory limit for the W3WP process

We run numerous ASP.NET applications on our webfarm, yet we saw a great deal of mistake access in case log:

Unable to get the exclusive bytes memory restriction for the W3WP procedure. The ASP.NET cache will certainly be incapable to restrict its memory usage, which might bring about a procedure reactivate.

We shops the internet site documents on a network share and also the application swimming pools running under the "Network Service" account. We did every preferred action (yet the trouble still shows up):

  • aspnet_regiis-- ga "Network Service"
  • cscript metaacl.vbs IIS:// Localhost/W3SVC/AppPools IIS_WPG RE
  • Add "Connect As" account to IIS_WPG team
  • Allow "Connect As" accont to logon as a solution
2
2022-06-07 14:34:01
Source Share
Answers: 2

Another opportunity if you relocated this solution or deprecated a domain name or something along those lines is that the small IIS_WPG approvals appointed to your metabase are for an obsoleted SID.

To figure out what approvals are in fact appointed:

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

If IIS_WPG is not detailed yet a SID is, run the complying with to add IIS_WPG:

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

The U (unsafe buildings read) need to suffice for this objective.

0
2022-06-08 02:36:44
Source

Did you reactivate the IIS solution after having implemented the manuscripts? This blog post additionally advises utilizing this declaration for providing approvals to the filters:

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

This mistake is brought on by a well-known concern with not enough approvals in your IIS metabase.

2
2022-06-07 14:55:06
Source