Reporting Services 2005 to .NET 4 infrastructure issues on the web server

Question

We had a custom ASP.NET 3.5 website that has been working for a long time, as well as an implementation of Reporting Services 2005. For example, in our IIS box (Win 2003 Server, IIS 6) we have our custom website. net, as well as Reporting Services Web Services and config'd Report Manager, all in one window. SQL Server 2005 databases (for RS and our own application) are located in a separate physical field.

Now we are trying to switch to .NET 4. Therefore, I installed the .NET 4 platform on our web server. We used VS2010 to upgrade our custom ASP.NET 3.5 site to 4 and drag the updated web.config to the web server. Our custom website works fine in .NET 4, but we can no longer run reports (either through our custom integration on our website, or even to the configured report manager URL).

In any case, we get the following error:

"Could not find permission set named" ASP.Net "

I did some searches for errors, but so far have not found anything that got home. Any thoughts, help would be greatly appreciated.

Answer 1

Verify that the default Reporting Services virtual directories (Reports and Report Server) are:

• Configures as applications, not just virtual directories
• Using a different application pool than your main site
• Target ASP.NET 2.0

When hosting RS 2005 under the parent site .NET 4.0, there are several other problems. Just in case you come across this too ...

1) The tag in the parent site web.config probably has the attribute targetFramework = "4.0". This can strangle .NET 2.0 when configuration settings are inherited by RS child applications. You can get around this by wrapping the contents of the parent web.config site with a location tag:

<configuration> <location path='.' inheritInChildApplications="false"> <!-- all the web.config goo --> </location> </configuration> 

2) "Path" /►yourApplicationRoot 022/eurl.axd/[Value] not found. mistakes. This is due to support for unlimited URLs added in ASP.NET 4. There is good documentation on how to solve this problem here: http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes#0.1__Toc256770153