InvalidOperationException: Failed to map the path '/'

[Dan]

This is interesting.  I was running VS2008 on a Vista Business pc, and had no problem with the Telerik Reporting controls.  Yesterday I upgraded to Windows 7 and started getting this problem:

Source File: c:\Users\mikeb\AppData\Local\Temp\Temporary ASP.NET Files\webportal\f4bbcb89\fa2cd45f\App_Web_no6xrxf_.40.cs    Line: 0

Stack Trace:


[InvalidOperationException: Failed to map the path '/'.]
   System.Web.Configuration.ProcessHostMapPath.MapPathCaching(String siteID, VirtualPath path) +719
   System.Web.Configuration.ProcessHostMapPath.GetPathConfigFilenameWorker(String siteID, VirtualPath path, String& directory, String& baseName) +19
   System.Web.Configuration.ProcessHostMapPath.System.Web.Configuration.IConfigMapPath.GetPathConfigFilename(String siteID, String path, String& directory, String& baseName) +37
   System.Web.Configuration.HostingPreferredMapPath.GetPathConfigFilename(String siteID, String path, String& directory, String& baseName) +75
   System.Web.Configuration.WebConfigurationHost.GetStreamName(String configPath) +8845430
   System.Configuration.Internal.DelegatingConfigHost.GetStreamName(String configPath) +13
   System.Configuration.BaseConfigurationRecord.InitConfigFromFile() +154

I found the prior posts on this error from 2008, where the issue was blamed on running the Telerik Reporting with VS2008 and Vista.  The "solution" being to run VS2008 as administrator.

I had no problem with VS2008/Vista, but now have the problem using VS2008/Windows7.  And, yes, running VS2008 as administrator does work around the problem.  (btw, I am using Telerik Reporting Q3 2008 SP2).

Has this been fixed in the latest version of Telerik Reporting?
Thanks,
Dan

[Steve]

Hi Dan,

There is nothing to fix as this is a security issue with Visual Studio and its build-in web server and not Telerik Reporting. In most cases Visual Studio has to be run with administrative privileges. In order to facilitate this and not forget, you may create a shortcut that always starts the IDE as administrator: for more details see the User Rights and Visual Studio article from MSDN.

Best wishes,
Steve
the Telerik team