.NET 3.5 SP1 Contains 404 Pages in an ASP.NET Web Application

Question

I had a problem with IIS 6.0 stopping working for an ASP.NET application after installing .NET 3.5 Service Pack 1.

I have two identical virtual dedicated servers. Installing SP1 on the first did not have a negative effect. Installing it on the second page caused ASP.NET pages to start returning 404 pages that were not found.

Static .html pages work on both servers.

Has anyone else experienced this?

Answer 1

This is a wide issue, so let's start with some troubleshooting questions:

• Based on your description, ASP.NET runtime does not capture your request and processes aspx files. You may need to re-register the asp.net pipeline with IIS using ASPNET_REGIIS -i.
• Is the app_offline.htm file removed from the application directory? I had this update before.
• Have you installed fiddler to follow the query to find out what exactly is being requested?
• Verify that ASP.NET is enabled in the IIS Administration Console under "Internet Service Extensions." Make sure that all versions of the framework are allowed to use all.

Well, let's start with those, and I hope we can help you solve the problem.

Answer 2

I recently saw people with this problem. This link may help.

And this one .

And a few more.

Answer 3

Is CustomErrors in your web.config set to On or RemoteOnly? If so, what do you get when you change it to Off?

Answer 4

I did not have this exact error with .NET 3.5 SP1, but they have seen similar in the past. You can usually solve it by opening a command prompt, going to the appropriate .NET folder and running ASPNET_REGIIS -i. In the case of .NET 3.5, there was no update of the core bits of the framework, so you really go to the .NET 2.0 folder, which can be found on my machine at:

\ Windows \ Microsoft.Net \ Framework \ v2.0.50727

Running ASPNET_REGIIS -i will re-register all ASP.NET libraries using IIS and should be equivalent to reinstalling the framework on this computer (as far as IIS is concerned)

Answer 5

Just to clarify. The last (4th) point asked by Dale was the problem. During the installation of Service Pack 1, the status "Status for ASP.NET" and "WebDAV" became prohibited in the "Web Services Extensions" section.

Why installing SP1 changed this setting on one server and not on another is a mystery that I will not mind (but do not expect) an answer ...

The second link provided by CodingTheWheel also received a response, so I will also mark this as an answer.

Answer 6

No one has done this before, so I will point out a trivial solution:
Have you already disabled the service pack and installed it (or the entire infrastructure) again?

Edit: @Kev:
A simple explanation: he said that the update works on one machine, but not on another. I had similar problems in the past, and reinstalling helped solve some of them. And this is trivial. What is my approach:
1. trivial 2. simple
3. headache

You are right, on productive systems you have to be careful, but this is his decision. And since it is a virtual server, it may be easy for him to copy it and try it as a test environment.