02 Nov 2007

I had an odd issue with trying to get the reportviewer control to work on some ASP.NET pages. I was using VS 2008 beta (but it was a 3.0 project so it should be the same as what you get in VS 2005), and running the solution through the VS web server. When going to the pages (which used local reports) I got the error:

Server Error in '/ATL' Application.
--------------------------------------------------------------------------------

Failed to map the path '/'.
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.InvalidOperationException: Failed to map the path '/'.

No idea what caused it but the moment I changed to run it on IIS it stopped. I did get an error on IIS about reporting services not being able to access the web.config file which was fixed by giving Network Service access to it, that didn't do any difference with VS 2008 web server but it did mean the reports worked. I suspect that it has to do with the way that reporting services locates the web.config file as VS 2008 server runs it as http://localhost:<random port>/<project name>/ where IIS runs it as http://localhost:<random port>.

Comments

vinod's picture

I am also facing the same issue. Did you find any solution to this??

Tim Kulp's picture

Hi,

You guys probably already tried this but just in case...did you try running Visual Studio as an admin? If you right click on the icon to start the application "Run As Administrator" should be an option if you are an admin on the machine. I had the same problem as you guys did and running VS as Admin did the fix for me.

Hope that helps!

Tim Kulp

Robert MacLean's picture

I didn't try that because VS 2008 (being that is what I am using) is supposed to work fine with UAC on Vista. I'll be revisiting that code in the next few weeks and will give it a try (also now that I have RTM vs the Beta 2 I was using might help).

CoolBreeze's picture

Thanks for the suggestion Tim. I'm not sure why this is happening, but I tried your suggestion on Vista with VS2005 and it worked.
Hellbinder's picture

So, I tried the run as admin option for visual studio and it worked perfectly. My question then is, what can I do to make it work with my account!? Where do I setup permissions or anything to make it work.
Any help would be appreciated.

Thank you for your reply which is the only one that helped me.

Visitor's picture

thank you, it is solve my issue

Gagne Padam's picture

Well, thank you. This also fixed my problem.....

Robert MacLean's picture

As I said the only solution I found was to run the site in IIS rather than in the Visual Studio web server.

Add new comment