Aspx Page Not Found Error Iis
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more iis aspx pages not working about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users deploy aspx page to iis Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each iis 7 aspx other. Join them; it only takes a minute: Sign up Why is IIS not serving aspx pages? up vote 6 down vote favorite 2 I'm deploying an ASP.NET application to Windows Server 2003 under IIS IIS is serving iis 6.0 aspx html pages fine but I get a page not found when I try and serve IIS pages asp.net iis iis-6 windows-server-2003 share|improve this question edited Jul 15 '15 at 8:00 Mikhail 6,63542136 asked Jun 17 '09 at 16:22 AJM 12k38120205 Did you setup the Virtual Directory for the asp.net page? –Dillie-O Jun 17 '09 at 16:23 add a comment| 6 Answers 6 active oldest votes up vote 15 down vote accepted You may need to
Iis 5.1 Aspx
"register" IIS for ASP.NET applications. As an administrator, run the command "%systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i". In addition, you may need to convert your web site to an application through the IIS management console. share|improve this answer answered Jun 17 '09 at 16:27 Jacob 46.8k1493166 add a comment| up vote 10 down vote By default, IIS has ASP support disabled in IIS6. A server running a member of the Microsoft® Windows® Server 2003 family supports application server functionality, with Microsoft ASP.NET as an option that you can enable when configuring the application server role. To deploy ASP.NET Web applications to a production server, you must be sure to enable the ASP.NET and Internet Information Services (IIS) roles on the production server before you distribute the application. See here for instructions to enable it: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/9fc367dd-5830-4ba3-a3c9-f84aa08edffa.mspx?mfr=true share|improve this answer answered Jun 17 '09 at 16:24 Rob Allen 9,62143966 add a comment| up vote 2 down vote Other possible reason could be Web Service Extensions, where ASP.NET version could have been disabled. My other post here explains steps to solve this. share|improve this answer answered Oct 12 '09 at 2:36 pencilslate 4,716124168 This was my problem. ASP pages would work but ASPX pages were 404 not found. Looked at web service extensions and low and behold ASP.NET v4.0xxx was disabled. Enabled it and it fired right up. –darin May 6 '13 at 18:07
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack
Iis Aspx Handler
Overflow the company Business Learn more about hiring developers or posting ads with us iis aspx 404 Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a iis aspx handler mapping community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ASPX Page Not Found (Error 404), though it exists? up vote 1 down vote favorite I http://stackoverflow.com/questions/1008151/why-is-iis-not-serving-aspx-pages have a C#.NET project and am having a problem with a single web forms, ASPX page when debugging my application. Most of my application works fine, but when I hit a particular page, I get an Error 404, resource not found. I don't understand this because the file does exist, and it exists in the path that is being referenced. And, I hit several other ASPX pages on the way to http://stackoverflow.com/questions/19671518/aspx-page-not-found-error-404-though-it-exists this one, without error. Now, I should mention that this particular page was only recently added to the project. My coworker, who added the page, says he was able to get the page to work, but we have different environments. So, I'm sure that has something to do with it, but I don't know what. Below are the known details regarding the differences between our environments. My environment Windows 8.1 IIS Express Visual Studio 2013 Co-workers environment Windows 7 IIS 7 Visual Studio 2012 We are both running with the same source code, as well as the same site and application pool settings in IIS, which are pointed to run time 4.0 and in classic mode. Does anyone here have any idea why this would happen, or what I might try to get past this? asp.net http-status-code-404 iis-express windows-8.1 share|improve this question asked Oct 30 '13 at 0:10 campbelt 82341739 1 Any routing in global.asax? –Zerkey Oct 30 '13 at 1:55 Thank you for the question. I am routing in global.asax because we also have an MVC component in our app. I can look into whether the routes are getting in the way. But, if that were it, wouldn't my co-worker also have the same problem? –campbelt O
platform and distributed applications A “404 File not found” issue caused by ASP.NET https://blogs.msdn.microsoft.com/asiatech/2011/12/07/a-404-file-not-found-issue-caused-by-asp-net-v4-0-extensionless-url-feature-on-iis-6-0/ v4.0 Extensionless URL feature on IIS 6.0 ★★★★★★★★★★★★★★★ APGC DSI TeamDecember 7, 20110 0 0 0 Symptom ======= After IIS is restarted, my customer received “404 File not found” error when he tried to visit his web site, e.g http://servername/ . If he visited http://servername/index.htm, iis aspx he would get the page successfully. The failed request in IIS log is: 2011-12-01 09:38:43 W3SVC1 127.0.0.1 GET / - 80 - 127.0.0.1 404 0 At the beginning, this problem seems to be related to the Default Document setting. But actually the server should return “Directory Listing Denied” iis aspx handler error instead of “404 File not found” error if Default Document is disabled. The problem may or may not disappear after IIS is restarted. Cause ===== After the debugging, we finally found the “404 File not found” error was returned because IIS could not find the file /eurl.axd/