Reporting Services 2000 broke by installing .NET 2.0 redistributable runtime files

We have RS 2000 running in our lab environment where I recently installed the .NET Framework 2.0 Redistributable Package. After installation, reporting services stopped working with the following error:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

I noticed the Version=2.0.0.0 part and went into the IIS properties for the /Reports directory and verified that 1.1 was selected and not 2.0.

Not sure why it appears 2.0 is being referenced when the site should be pointing to 1.1 libraries.

Any ideas would be appreciated.

Make sure you check both virtual folders: /Reports and /ReportServer. When you go to the properties of these virtual folders, go to application configuration and check all script maps. Make sure there's no v2.0 DLLs in the script maps.|||If you are running Windows XP or you have Reporting Services installed in the same application pool as an ASP.NET 2.0 application, then this will happen. You can't run two version of the .NET Framework in the same IIS process.|||I tried both posted solutions and neither worked, although they were good ideas. Both the /Reports and /ReportServer directores have the 1.1 binaries in the Application Mappings tab in IIS. Of interest is the /Reports directory has many application extensions listed and no wildcard maps. The /ReportServer directory has the opposite, no application extensions and one wildcard mapping. Regardless, they all point to 1.1 binaries.

I created a new application pool and put the /Reports and /ReportServer in that pool and am getting the same error.
|||In addition, this event was logged in the Application Events. Still appears to be using the 2.0 libraries yet I don't know why:

Event code: 4010
Event message: An unhandled security exception has occurred.
Event time: 12/1/2005 4:54:28 PM
Event time (UTC): 12/1/2005 9:54:28 PM
Event ID: 37a8c59bd4d14536ac63fdd0b43185d3
Event sequence: 7
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-127779471911380892
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\
Machine name: TLCB1
Process information:
Process ID: 1864
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Request information:
Request URL: http://tlcb1/reports/Pages/Folder.aspx
Request path: /reports/Pages/Folder.aspx
User host address: 10.125.124.17
User: xxxx\yyyyy
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Custom event details:

For more information, see Help and Support Center at
|||After working with Microsoft support for weeks on this (yes overseas support isn't very expeditious), it turns out it was a problem with a content management ISAPI plugin. The plugin was coded to always run in the context of the latest .net framework version. Since the plugin ran in the default application pool, every app in the default pool then would use the 2.0 framework instead of the 1.1 framework, regardless of what was set for each site.

The solution was to put the content management ISAPI plugin in its own app pool with nothing else. That allow the other apps to use the framework of their specification.
|||

I just updated my Windows 2003 server running Reporting Services 2000 with Net 2.0 and had the same error. I solved it by just selecting the old version 1.1.4 from the ASP.Net settings under the properties tab on IIS. Seems it allows you to select which version to run at each level of a Web/Sub Web. Make sure to select the reportserver and the report sub webs.

Hope this helps.

Tim

|||I had this problem when i've installed MSSQL 2005 and tried to use ReportServer. First I've tried to disable .NET 2.0, but it didn't help. so i uninstalled .net 2.0 and restarted IIS server. it worked. after i've downloaded .net 2.0 from microsoft.com, installed it. Everything works perfect. seems like the .net packege that is distributed with SQL 2005 is broken or something like that.