The Metabase Explorer tool for modifying metabase permissions on the IIS Admin Objects is available

Important This article contains information about how to edit the metabase. Before you edit the metabase, verify that you have a backup copy that you can restore if a problem occurs. For information about how to do this, see the "Configuration Backup/Restore" Help topic in Microsoft Management Console (MMC).


Previously, the MetaAcl.vbs tool was available for download to modify the default permissions that are set on an Internet Information Services (IIS) metabase. The MetaAcl.vbs tool is no longer available. Instead, use the Metabase Explorer tool that is included in the IIS 6.0 Resource Kit.

You might have been redirected to this Microsoft Knowledge Base article from the following IIS error message:
System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase. The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see
 You receive this error message because the permissions to the metabase are insufficient, or because the permissions are set incorrectly.  

To help resolve this error, use the Metabase Explorer tool to modify the metabase permissions. For more information about the Metabase Explorer tool and the IIS 6.0 resource Kit Tools, please see:

The IIS 6.0 Resource Kit Tools

More Information

You can download the Metabase Explorer tool as part of the IIS 6.0 Resource Kit Tools from the following location:

 If you are using ASP.Net 2.0 and you must grant metabase permissions to a Windows user account, run the ASP.NET IIS Registration Tool command together with the -ga option. For example, the following command grants the Windows user account <WindowsUserAccount> permissions to the IIS metabase:
aspnet_regiis -ga <WindowsUserAccount>
Warning If you edit the metabase incorrectly, you can cause serious problems that may require that you reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk.

Note Always back up the metabase before you edit it.