I installed Report Services 2005 on XP Pro, and when trying to access the http://localhost/Reports directory, I receive this error: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 http://support.microsoft.com/?kbid=267904. I ran the aspnet_regiis ga <WindowsUserAccount> , still nothing. I went in to IIS and checked the settings, and everything for the Reports directory looks just like the IISHelp directory(which I'm able to view using http://machinename/IISHelp I did restart IIS after apply the aspnet_regiis also. Any other thoughts on what I can look at to resolve this issue? Thanx, Mike

What is your ASP.NET account (you can check this by opening the RS configuration tool, and click on "Web Service Identity" tab)? Can you try the Metaacl tool and see if the account has read access? Do you get the same error when accessing http://localhost/reportserver?

James, The asp.net account is machinename\ASPNET I'm not familiar with the Metaacl tool. And yes, I get the same result for http://localhost/reportser I did create a hello world asp.net page on the machine, and that works fine. Thanx, Mike

Metaacl tool is in the link you provided :)http://support.microsoft.com/?kbid=267904

I tried metaacl and still nothing. Here's what I entered: metaacl http://localhost/Reports mydomain\userid It returned -2147221020 And, still cannot access http://localhost/Reports

You need to run the tool with the correct syntax. Try cscript metaacl.vbs IIS://localhost/w3svc

James, Thanx for the tip! Here's what I received back ( I have replaced the domainname with the word domain) C:\Downloads\Microsoft\iis>cscript metaacl.vbs IIS://localhost/w3svcMicrosoft (R) Windows Script Host Version 5.6Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. DOMAIN\IUSR_DOMAIN Access: R EBUILTIN\Administrators Access: RWSUEDEveryone Access: EDOMAIN\VS Developers Access: RWSUE And, when I entered cscript metaacl.vbs IIS://localhost/w3svc DOMAIN\mjvoisse I received the following:No ACE in ACL for DOMAIN\mjvoisse

I don't see your ASPNET user have read permission. Try adding it cscript metaacl.vbs IIS://localhost/w3svc "machinename\ASPNET" R If there are still permission problems, does it work if you temporarily set your ASPNET user to an admin?

WooHoo! This worked. Now I get the Reports page. Of course, I have no management choices, just the plain home page. Shouldn't I be able to see more? I'm thinking there are still some issues with rights. I appreciate your time and effort with this James. SQL Server Reporting Services Home Home| MySubscriptions| Help

Your login accountneeds to be a "Content Manager". You can add yourself to this role using the report manager. You may need to login as an admin to do that.

Let say my machinename is 2345, my domain is 123, and my userid is 789 I have typed this at the command prompt cscript metaacl.vbs IIS://localhost/w3svc "2345\ASPNET" R it says it has changed something in metabase, I've also done this aspnet_regiis -ga 123\789 and it says it has already registered that userid(789) for ASPNET. I've stopped the IIS, started it again, restart my PC, but..... unfortunately...... the problem still persist Failed to access IIS metabase. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: 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 http://support.microsoft.com/?kbid=267904.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

After doing the steps highlighted and countless other things I still have the same problem. Did you mange to find out the problem? Im exactly where you were?

We run into the same problem and went through the following sequence of steps to resolve it: 1. Ran cscript metaacl.vbs IIS://localhost/w3svc "machinename\ASPNET" R. This did not fix the problem. We verified that our ASPNET account had RWSUED and moved to step 2. 2. Ran aspnet_regiis ga <WindowsUserAccount>. This did not fix the problem either. We then guessed that the developer who was experiencing this issue probably installed IIS on top of Visual Studio 2005. So we decided to repair the framework. (step 3) 3. Ran dotnetfx.exe /t:c:\temp /c:"msiexec.exe /fvecms c:\temp\netfx.msi" Finally, that did the trick.

thank you jcvecka, muchly appreciated I could kiss you, hehe

Hi, Your steps are logical and looks like it woeked too. But my issue is: I am down to your option 3 and cannot run dotnetfx.exe as I have already installed 3.5 and SP1 too Any idea what can be done - besides uninstalling everything and redoing IIS, VS05 and then VS08 + SP1 Thanks

I tried to do the as explained above but some of it was a bit too complicated to understand such whether I even have a DOMAIN in windows XP or not because I'm using Workgroup.. accessing the http://localhost/localstart.asp was a bit odd as I don't know what to enter in the popup window's username and password since I didn't set a password for my windows admin account..Using the cscript metaacl.vbs IIS://LOCALHOST/W3SVC Workgroup\John Wayne RW was a bit odd as well because it returned me "ACE for Workgroup\John added" so I didn't get whether only John was added and not John Wayne, it seems like it doesn't allow space between names..Anyway I got the "Failed to access IIS metabase" fixed by this simple process below..If you're using .Net Framework 2.0, here is the solution. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727, and run aspnet_regiis -i Restart IIS.Thanks.

Thank you so much, Critcalx2!That really did the trick!

Thanks to all , Finally I find, with all the reference and concluded as below. Installation must be same order as below Install OS – XP and Install IIS 5 or 6 install dotnetfx ( DotNet Framework 2.0, 3.0, 3.5) If miss the above order… Try Following points for the Error : 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 http://support.microsoft.com/?kbid=267904. · Download the Metaacl.exe · Refer link http://support.microsoft.com/kb/326902/ Copy the Metaacl.vbs file to the %systemdrive%\Inetpub\Adminscripts directory. Click Start, click Run, type CMD, and then click Run to open a command prompt. At the prompt, run the following command to change to the Adminscripts directory: 4. c:\cd Inetpub\Adminscripts To modify the parameters located at IIS://LOCALHOST/W3SVC, run the following command: 6. c:\Inetpub\Adminscripts>cscript metaacl.vbs IIS://LOCALHOST/W3SVC mydomain\mydomainaccount RW 7. You receive the following response: ACE for mydomain\mydomainaccount added. You can use Metaacl.vbs to add the following rights for any user: R - Read W - Write S - Restricted Write U - Unsecure Properties Read E - Enumerate Keys D - Write DACL (permissions) · Then Follow the method Note If you are using ASP.Net 2.0 and you must grant metabase permissions to a Windows user account, do not use the MetaAcl tool. Instead, 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> C:\Documents and Settings\10306>cd\ C:\>cd WINDOWS\Microsoft.NET\Framework\v2.0.50727 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -ga KEMWELL\10306 Start granting KEMWELL\10306 access to the IIS metabase and other directories us ed by ASP.NET. Finished granting KEMWELL\10306 access to the IIS metabase and other directories used by ASP.NET. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>cd\ C:\>cd dotnetfx C:\dotnetfx>dotnetfx.exe /t:c:\temp /c:"msiexec.exe /fvecms c:\temp\netfx.msi" C:\dotnetfx>cd\ C:\>cd WINDOWS\Microsoft.NET\Framework\v2.0.50727 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i Start installing ASP.NET (2.0.50727). ........................................... Finished installing ASP.NET (2.0.50727). C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727> Now Restart IIS. And browse your file. After a week headhek comes to an end, and still problem remain as for following issues: 1. Windows 7 OS with IIS 7, 2. Remote connection to Database.

Thank uuuuuuuuuuuuuuuuuuuuuu It worked for me Thanks a lotKuldeep Choudhary Software development Division, Asterisk Group of Computer Engineers

Wow, Really worked for me , this is an accurate solution.

This worked for me! I installed IIS after Visual Studio, as someone mentioned in an earlier post...but this solution was quick and easy. Thanks Criticalx2

I encountered this error after installing IIS after ASP.NET - none of these solutions worked for me - finally simply running aspnet_regiis.exe /i to install aspnet in IIS worked like a champ.

Read a lot of complicated (although no doubt necessary for a lot of people) steps to resolve this problem, but I tried your's first because it was the simplest - and it worked. THANKS! I'd recomment trying this folks before undertaking anything more involved.