Recently, I ran into a server which was running ColdFusion, but wasn’t ASP.NET extensions. It was really confusing because ASP.NET 2.0 was listed as a possible extension under IIS. But, after we copied over an ASP.NET website, the only result was a 404 page not found.
After looking through the IIS logs, I found the 404 entry. There was sub-status code of 2 (Web service extension lockdown policy prevents this request).
So, I started to look up how “service extensions” worked. Which didn’t take much …
After a little looking with google, I ran aground the ability to enable and disable ISAPI extensions with the command line.
Unfortunately, ASP.NET had been turned off. I would guess that it had been done with purpose, as no ASP/ASP.NET application websites were running before. But, the new website needed ASP.NET. So, with a few command line statements it was turned back on (iisext) …
