The article http://securinga.com/2004/07/unable-to-get-private-bytes-memory.html provides a solution for the "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". Running Metaacl.vbs "IIS://localhost/W3SVC/AppPools" ACC-MSAPP01\IIS_WPG U does solve the problem. However, when the server is rebooted, the problem occured again. The orphaned SID is from the IIS_WPG account on the Microsoft Application
Center cluster controller. Microsoft Application Center synchronizes all servers in the webfarm and causes this problem. Application Center synchronizes the metabase security to other clustermembers but uses its own IIS_WPG, e.g. server01\IIS_WPG. The server01\IIS_WPG
is reflected on e.g. server02 as the SID since it does not recognize this local account. When server02 is rebooted after running Metaacl.vbs "IIS://localhost/W3SVC/AppPools" ACC-MSAPP01\IIS_WPG U, it gets is IIS Metabase synchronized from server01 and the
problem occurs again. A solution would be to give a group that contains all application process accounts the U right, for example: Metaacl.vbs "IIS://localhost/W3SVC/AppPools" domainName\AllProcessAccounts U However, this seems to be a bug in Application Center
but the workaround described does the job.
Microsoft Support confirmed that is a known issue in Application Center. They are not sure yet on how they want to solve the problem. The suggested workaround is to use a global account, like suggested above, or to use the NETWORK SERVICE account in the Application
Pools.
Thanks for the heads up on the this. I have posted an
alternative workaround to your solution... it isn't necessarily better but it may prove to be useful in certain circumstances.
In addition to the former stated workaround, Microsoft Support has stated that: "Use on of the predfined AppPool identities NetworkService, LocalService or local system. Another way could be to use a Domain Group adding to the IIS_wpg group and create the ACL's
for this group in the Metabase."
mgebbinck
Member
25 Points
5 Posts
Solution for the error: "Unable to get the Private Bytes Memory Limit for the W2WP Process"
Oct 06, 2004 02:54 PM|LINK
mgebbinck
Member
25 Points
5 Posts
Re: Solution for the error: "Unable to get the Private Bytes Memory Limit for the W2WP Process"
Oct 07, 2004 09:14 AM|LINK
Securinga.co...
Member
5 Points
1 Post
Re: Solution for the error: "Unable to get the Private Bytes Memory Limit for the W3WP Process"
Oct 07, 2004 11:49 AM|LINK
mgebbinck
Member
25 Points
5 Posts
Re: Solution for the error: "Unable to get the Private Bytes Memory Limit for the W3WP Process"
Oct 07, 2004 12:03 PM|LINK
AhmedHussein
Member
4 Points
2 Posts
Re: Solution for the error: "Unable to get the Private Bytes Memory Limit for the W2WP Process"
Mar 23, 2008 11:01 PM|LINK
find the fix for this error in my blog below. I had the same error on production servers and it works fine.
http://geekswithblogs.net/Ahmed_Hussein_blog/archive/2008/03/23/120710.aspx
Regrads
Ahmed Hussein
asp.net custom domain service account application pool iis 6.0 asp.net IIS6.0
carloc
Member
51 Points
10 Posts
Re: Solution for the error: "Unable to get the Private Bytes Memory Limit for the W2WP Process"
Jul 09, 2008 11:54 AM|LINK
The original link to this solution is at http://blogs.msdn.com/carloc/archive/2006/09/20/unable-to-get-the-private-bytes-memory-limit-for-w3wp-exe-process.aspx