mrpib
IS-IT--Management
- Dec 27, 2001
- 17
We used to host our staging sites on a 2000 Server box and moved them over to a 2003 Standard server. All of the html sites work just fine but the ASP sites are not.
We have ASP.Net v1.1.4322 allowed in the Web Service Extensions. Under the properties of the site's HTTP headers is listed X-powered by ASP.Net. In the ISAPI filters, we have fpexedll.dll added and that is it. Execute permissions is set for Scripts & Executables. In the documents tab we do have listed default.asp in the middle window. I tried mimicing everything that is on the old server but obviously there is a step not covered.
The error we're getting is:
HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)
The site that was migrated over is not the only one effected. I had one of the developers mess around & created a test.asp with no luck as well. So there is something not configured in IIS that is the problem & not the actual staging site.
Any thoughts from the IIS 6 & ASP experts?
- Pibs
We have ASP.Net v1.1.4322 allowed in the Web Service Extensions. Under the properties of the site's HTTP headers is listed X-powered by ASP.Net. In the ISAPI filters, we have fpexedll.dll added and that is it. Execute permissions is set for Scripts & Executables. In the documents tab we do have listed default.asp in the middle window. I tried mimicing everything that is on the old server but obviously there is a step not covered.
The error we're getting is:
HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)
The site that was migrated over is not the only one effected. I had one of the developers mess around & created a test.asp with no luck as well. So there is something not configured in IIS that is the problem & not the actual staging site.
Any thoughts from the IIS 6 & ASP experts?
- Pibs