Web 服务器上的 Reporting Services 2005 到 .NET 4 框架的问题

发布于 2024-10-14 03:47:43 字数 530 浏览 0 评论 0原文

我们的自定义 ASP.NET 3.5 网站与 Reporting Services 2005 实现一起运行了很长时间。也就是说,在我们的 IIS 机器(Win 2003 Server、IIS 6)上,我们有自定义的 .net 网站以及 Reporting Services Web 服务和报表管理器配置,所有这些都在同一个机器上。 SQL Server 2005 数据库(用于 RS 和我们自己的应用程序)位于一个单独的物理盒子上。

我们现在正在尝试升级到 .NET 4。因此我在我们的 Web 服务器上安装了 .NET 4 框架。我们使用 VS2010 将自定义 ASP.NET 3.5 站点升级到 4,并将更新后的 web.config 推送到 Web 服务器。我们的自定义网站在 .NET 4 下运行良好,但我们无法再运行报告(通过我们网站中的自定义集成,甚至通过访问报告管理器配置的 URL)。

无论哪种情况,我们都会收到以下错误:

“找不到名为“ASP.Net”的权限集”

我一直在对该错误进行一些搜索,但到目前为止还没有找到任何有意义的内容。任何想法、帮助将不胜感激。

We have had custom ASP.NET 3.5 website running for a long time along with a Reporting Services 2005 implementation. So, that is, on our IIS box (Win 2003 Server, IIS 6), we have our custom .net website and the Reporting Services web services and Report Manager config'd, all on the same box. The SQL Server 2005 databases (for RS and our own app) are on a separate physical box.

We are now attempting to upgrade to .NET 4. So I installed the .NET 4 framework on our web server. We used VS2010 to upgrade our custom ASP.NET 3.5 site to 4 and pushed over the updated web.config to the web server. Our custom web site is working great under .NET 4, but we are no longer able to run reports (either via our custom integration in our website or even by going to the Reports Manager configured URL).

In either case we get the following error:

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

I've been doing some searches on the error, but so far haven't found anything that's hitting home. Any thoughts, help would be greatly appreciated.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

恏ㄋ傷疤忘ㄋ疼 2024-10-21 03:47:43

确保 Reporting Services 虚拟目录(默认情况下为“Reports”和“ReportServer”):

  1. 而不仅仅是虚拟目录
  2. 使用与主站点不同的应用程序池
  3. 目标 ASP.NET 2.0

配置为应用程序, 在 .NET 4.0 父站点下托管 RS 2005。以防万一您也遇到这些...

1) 父站点的 web.config 中的标记可能具有 targetFramework="4.0" 属性。当您的子 RS 应用程序继承配置设置时,这可能会阻塞 .NET 2.0。您可以通过使用位置标记包装父站点 web.config 的内容来解决此问题:

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

2) “未找到路径 '/[yourApplicationRoot]/eurl.axd/[Value]'。”错误。这与 ASP.NET 4 中添加的无扩展 URL 支持有关。这里有关于如何解决此问题的良好文档:http://www.asp.net/learn/whitepapers/aspnet4/writing-changes#0.1__Toc256770153

Make sure the Reporting Services virtual directories ("Reports" and "ReportServer" by default) are:

  1. Configured as applications, not just virtual directories
  2. Using a different app pool than your main site
  3. Target ASP.NET 2.0

There are several other issues commonly encountered while hosting RS 2005 under a .NET 4.0 parent site. Just in case you run into these too...

1) The tag in the parent site's web.config likely has a targetFramework="4.0" attribute. This may choke .NET 2.0 when the configurations settings are inherited by your child RS apps. You can get around this by wrapping the content of the parent site's web.config with a location tag:

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

2) "Path '/[yourApplicationRoot]/eurl.axd/[Value]' was not found." errors. This has to do with extensionless URL support added in ASP.NET 4. There is good documentation on how to address this here: http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes#0.1__Toc256770153

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文