Failed to access IIS metabase error after installing reporting services

Today one of my friend installed reporting services on his machine and got this error while trying to access the report server -

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/

image

Solution provided in support link solved the problem, we just needed to give permissions to the ASPNET account by sunning aspnet_regiis -ga ASPNET command within the .net framework 2.0 directory.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -ga ASPNET

image

Although I am not very sure why this error occurred, some posts mention that this error occurs if IIS was installed after .net 2.0 but I don't think this was the cause in our case but anyway's all's well if it ends well.

Published Tuesday, September 23, 2008 2:15 PM by akjoshi

Comments

# re: Failed to access IIS metabase error after installing reporting services

Monday, December 14, 2009 2:13 PM by Filipe Monteiro

thanks a lot! solved my problem.

# re: Failed to access IIS metabase error after installing reporting services

Thursday, April 29, 2010 1:44 AM by Rajkumar Varatharaju

Cool solution that solved my problem after simple cmdline execution !!!

Many thanks again.

# re: Failed to access IIS metabase error after installing reporting services

Thursday, July 08, 2010 2:48 AM by Vamsi

Thanks that was very useful, it solved my problem

# re: Failed to access IIS metabase error after installing reporting services

Saturday, July 31, 2010 8:05 AM by Vinay

Sorry My problem not yet solved.

After publishing When i browse in local system it is working properly, but when i browe from other machines it is not comming.

I have used Web Services.

Please help me if any one is having solution to this.....

# re: Failed to access IIS metabase error after installing reporting services

Wednesday, December 28, 2011 2:39 AM by Rahal Bamunusinghe

Thanks for lot... This is happen when ACL (Access Control List) denied to access IIS for user ASPNET. ACL is the core place of holding security instructions. Your code grants access permission for user ASPNET. Excellent.

Leave a Comment

(required) 
(required) 
(optional)
(required)