.NET 3.5 Service Pack 1 导致 ASP.NET Web App 出现 404 页面
在安装 .NET 3.5 的 Service Pack 1 后，我遇到了 IIS 6.0 停止为 ASP.NET 应用程序工作的问题。
我有两台相同的虚拟专用服务器。 在第一个上安装 SP1 没有产生不利影响。 将其安装在第二个上会导致 ASP.NET 页面开始返回 404 页面未找到。
静态 .html 页面在两台服务器上都工作正常。
还有其他人经历过这个吗？
I have a problem with IIS 6.0 ceasing to work for an ASP.NET application after installing Service Pack 1 for .NET 3.5.
I have 2 identical virtual dedicated servers. Installing SP1 on the first had no adverse effect. Installing it on the second caused ASP.NET pages to start returning 404 page not found.
Static .html pages working okay on both servers.
Has anybody else experienced this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
以前没有人这样做过，所以我将指出一个简单的解决方案：
您是否已卸载 Service Pack 并重新安装（或整个框架）？
编辑：@Kev：
简单解释：他说更新可以在一台机器上运行，但不能在另一台机器上运行。 我过去也遇到过类似的问题，重新安装有助于解决其中一些问题。 而且做起来很简单。
这就是我的方法：
1. 琐碎
2.简单
3. 头痛
你是对的，在生产系统上你必须小心，但那是他的决定。 而且因为是虚拟服务器，或许他很容易复制过来，先作为测试环境尝试一下。
No-one did before, so I'll point to the trivial solution:
Have you already de-installed the Service Pack and re-installed it again (or the whole framework)?
Edit: @Kev:
Easy explanation: He said the update works on one machine, but not on the other. I had similar problems in the past and re-installing helped to solve some of them. And it is trivial to do.
That's my approach:
1. trivial
2. easy
3. headache
You are right, on productive systems you must be careful, but that's his decision. And because it is a virtual server, maybe it is easy for him to copy it and try as a test environment first.
这是一个广泛的问题，所以让我们首先提出一些故障排除问题：
好吧，让我们从这些开始，希望我们可以引导您解决问题。
This is broad problem, so let's start by asking some troubleshooting questions:
Well, let's start with those and hopefully we can guide you to the problem.
我在 .NET 3.5 SP1 中没有遇到过这种确切的错误，但过去也见过类似的情况。 通常可以通过打开命令提示符、转到相应的 .NET 文件夹并运行 ASPNET_REGIIS -i 来解决。 对于 .NET 3.5，框架的主要部分没有更新，因此您实际上会转到 .NET 2.0 文件夹，在我的计算机上可以在以下位置找到该文件夹：
\Windows\Microsoft.Net\ Framework\v2.0.50727
运行 ASPNET_REGIIS -i 将向 IIS 重新注册所有 ASP.NET 库，并且应该相当于在给定计算机上重新安装框架（就 IIS 而言）
I have not had this exact error with .NET 3.5 SP1, but have seen similar occur in the past. Typically it can be resolved by opening a command prompt, going to the appropriate .NET folder and running ASPNET_REGIIS -i. In the case of .NET 3.5 there wasn't an update to the main bits of the framework, so you'd actually go to the .NET 2.0 folder, which on my machine can be found at:
\Windows\Microsoft.Net\framework\v2.0.50727
Running the ASPNET_REGIIS -i will re-register all the ASP.NET libraries with IIS, and should be the equivalent of a re-install of the framework on a given machine (as far as IIS is concerned)
我最近见过很多人遇到这个问题。 此链接可能会有所帮助。
还有这个< /a>.
还有其他一些。
I've seen various people with this problem recently. This link might help.
And this one.
And a few others.
web.config 中的 CustomErrors 是否设置为 On 或 RemoteOnly？ 如果是这样，当您将其更改为“关闭”时会得到什么？
Is CustomErrors in your web.config set to On or RemoteOnly? If so, what do you get when you change it to Off?
只是为了澄清。 戴尔给出的最后（第四）点就是问题所在。 在安装 SP1 期间，ASP.NET 和 WebDAV 的状态在 Web 服务扩展下设置为“禁止”。
为什么安装 SP1 在一台服务器上更改此设置而不是另一台服务器上的设置是一个谜，我不介意（但不期望）得到答案...
CodingTheWheel 提供的第二个链接也有答案，所以我也将将此标记为答案。
Just to clarify. The last (4th) point given by Dale was the problem. During the installation of SP1 the Status for ASP.NET and WebDAV became set to Prohibited under Web Service Extensions.
Why the installation of SP1 changed this setting on one server and not the other is a mystery that I wouldn't mind (but not expect) an answer to...
The second link provided by CodingTheWheel also had the answer so I'm also going to mark this as an answer.