PROBLEM DESCRIPTION =================== I can run ASP.NET applications on the server, however I have noticed that when I do there is an asp 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. Error 0x80070005".
ENVIRONMENT =========== - Windows Server 2003 - .NET Framework 1.1
SUMMARY of TROUBLESHOOTING ========================== 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 - cscript metaacl.vbs IIS://Localhost/W3SVC/Filters IIS_WPG RE
Warning: The path is case sensitive - type exactly as above; after you run this command restart the IIS services and see if this corrects the problem.
Update: here is an update on this matter: http://blogs.msdn.com/carloc/archive/2009/01/27/unable-to-get-the-private-bytes-memory-limit-for-the-w3wp-process-reloaded.aspx
Carlo
Hi Carlo,
There's bits of information around pointing this error to a metabase permissions problem, but no-one has given a soloution... until now.
This solution works great.
Thanks,
Ady
Worked like a charm!
Thanks.
I still run into this problem on ASP.NET 2.0 even though I have used the following command to give the domain account access to metabase.
aspnet_regiis –ga <WindowsUserAccount>
Kris, you probably are still missing something, try the following:
- aspnet_regiis -ga <account>
- cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE
- add the account specified in the “Connect As” dialog to the IIS_WPG group
- grant the account specified in the “Connect As” dialog the "Logon as a service" right
If this still does not help you may consider opening a support call online from http://msdn2.microsoft.com/en-gb/aa570318.aspx (this is the UK page, chose your locale through the language dropdown at the top of the page.
HTH
I get this error on IIS 6.0 with a domain account that controls the pool.
The MSDN documentation says that MetaACL should not be used in this case and to run aspnet_regiis –ga <WindowsUserAccount> which was done from the start on this server. Any toughts?
Hi Patrick, if "aspnet_regiis -ga" does not help I would try metaacl anyway (of course backup your metabase first); if this still does not help I guess you'll need deeper troubleshooting with CSS help if you like...
Besides throwing the error, does anyone know what the symptoms of this problem (if any) are?
The fix did the trick for us (thank you) and I am wondering if we will see any performance improvement from our web servers.
We had this problem too. I didn't feel comfortable to run a script without knowing if that really was my problem. Also Microsoft says that if you run asp.net 2.0 you shouldn't run this script but you should aspnet_regiis -ga for the user which runs the application pool.
That's why I wanted know if the error was really security related in my case. The strange thing was that I couldn't find anything about metabase security. I found some Microsoft articles which say that the metabase security is implemented on file level but I couldn't find anyting about security on metabase nodes.
If you want to know the current permissions on a metabase node you have two options:
1. run metaacl.vbs on a specific node , for example: metaacl.vbs IIS://Localhost/W3SVC/AppPools this command doesn't make any modifications but only shows you the current permissions.
2. use metabase explorer (download: http://support.microsoft.com/kb/840671).
With these tools you can view the current permissions. You can also use this tools too change permissions.
To solve the problem described in this forum you should give IIS_WPG permissions as described above.
I had this in the following scenario:
- Windows Server 2k8 Standard
- IIS 7.0
- ASP.NET 2.0 (native)
- ASP.NET 1.1 (installed)
When I try to run an app based on ASP.NET 1.1 the message is logged in application log.
I followed the solution described above but it didn't work.
Any toughts?
Tks
Hello Paulo, sorry for my late reply.
The command cannot work on IIS7 because we do not have the metabase anymore but rather a completely different configuration storage (xml based as it happens with ASP.NET), so in IIS7 the error may have a different cause and for sure a different solution.
Honestly I have not see it yet reported into CSS so I unfortunately I cannot give some "ready to use" advice at the moment, we would need to investigate the problem deeply and cannot be done through a blog... my suggestion is to open a Support Call with us (http://support.microsoft.com) and an Engineer will assist you on this matter.
Gr8 post
its works perfect
Thqu soo much