Failed to access IIS metabase problem Solution
Possible
Cause:-
When you install IIS AFTER .NET 2.0 framework, the rights of the ASPNET user had not been set correctly.
Resolution
Repair (Uninstall if repair does not work for you) .NET Framework 2.0
When you install IIS AFTER .NET 2.0 framework, the rights of the ASPNET user had not been set correctly.
Resolution
Repair (Uninstall if repair does not work for you) .NET Framework 2.0
Simply run the following from
command line to reset the IIS registry settings for aspnet user. Usually
framework directory for .Net Framework 2.0 resides under C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Introduction:
Here I will explain how to solve the problem “Failed to access IIS metabase ASP.NET” when we try to browse website using asp.net
Here I will explain how to solve the problem “Failed to access IIS metabase ASP.NET” when we try to browse website using asp.net
Description:
In my machine I tried to access one of the website from IIS at that time I got error like “Failed to access IIS metabase ASP.NET”. I realized that problem because of process model user account (in our case, ASPNET) does not have the correct user rights for the required system files and folders to run the ASP.NET worker process and apparently there is a bug in the ASP.NET install.
In my machine I tried to access one of the website from IIS at that time I got error like “Failed to access IIS metabase ASP.NET”. I realized that problem because of process model user account (in our case, ASPNET) does not have the correct user rights for the required system files and folders to run the ASP.NET worker process and apparently there is a bug in the ASP.NET install.
To
solve this problem follow below steps:
Open
visual studio command prompt and type below command and run
aspnet_regiis -ga
machinename\ASPNET
|
After run the above command Reset
the IIS and test the application that resolve your issue.
If above command doesn’t resolve
your problem then try to run below command in visual studio command prompt
aspnet_regiis -i
|
Alternatively we can run above
command from our windows command prompt also
Go to the Start menu and open Run and enter and
click Ok
%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe
–I
|
After that Reset the IIS
and test the application that resolves your issue
Comments