Description of the Issue

When trying to run an ASP.NET application on a Web Server, the customer receives an error stating that there was a problem connecting/accessing the IIS metabase.

Example:
 
	Failed to access IIS metabase	''There are other possible error messages and they will be added as we encounter them.''

Cause of the Issue

The most common cause of this issue is due to installing IIS on the server after .NET Framework 2.0 (which include ASP.NET version 2.0.xxxx or above) has already been installed.  When IIS is installed after .NET Framework 2.0, the permissions do not get properly set for the ASPNET user.  Repairing these permissions should resolve the issue.

Resolving the Issue

There are currently two possible solutions to resolve this issue:

Repair the IIS Registry Settings for the ASPNET User

In most cases, simply running the following command from the Windows Run Command Line will reset the IIS registry settings for the ASPNET user and resolve the issue.
 
To run the command:
  1. Go to the START menu and select "Run..." to open a Windows Run Command Line
  2. Copy the following command into the Windows Run Command Line field:
    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i
  3. Press Enter or click the "OK" button to run the command.
  4. When the black Windows Command Console disappears, try your application again.  The issue should be resolved.

Reinstall the Microsoft .NET Framework 2.0

If the above option does not work for you, then you may have to take the slower, more painful route.  This will require you to completely uninstall the Microsoft .NET Framework 2.0 via "Add/Remove Programs" and reinstall it from scratch (including security fixes/updates) from Windows Updates.  This will probably require a little time and a few reboots, so plan accordingly.

Other References

Microsoft:
Other:
 

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: December 10, 2016