I generated a new web site in IIS. Under the new web site, there are some asp .net 2.0 applications. Tomcat is also running on the same server and they are working correctly.
But when I try to open an asp .net application, I am taking page can not be found error message. Then I changed the configuration settings of asp .net version from 2.0 to 1.1 then it is not giving page can not be found message but it gives an error message about web config. What can I do?
You haven't given many details. This could be a couple of things:
you have used an incorrect URL
you have used an incorrect protocol (i.e. http instead of https)
you are specifying a directory but you have no default document set up (i.e. you are going to http://mywebsite/myvirtualdir/, but you have no default.aspx)
you haven't installed ASP.NET so there are no handlers for aspx pages
until you give more details then no-one can say for sure what your problem is.
Related
I have deployed MVC5 project that I converted to the application under Default Web Site as you can see here. I think, this is a standard procedure. When I open the default URL http://intranet.company.com the server do a redirection to http://172.20.20.133/intranet/. Physical path of the intranet application is C:\inetpub\wwwroot\intranet. I also tried to move deployed project directly under Default Web Site without any virtual directory but with the same result, it was redirected to http://172.20.20.133/intranet/.
Somebody knows what's wrong? Thanks in advance.
When I am trying to run the classic asp application over iis7.5 I am getting error "The type of page you have requested is not served because it has been explicitly forbidden. The extension '.asp' may be incorrect. Please review the URL below and make sure that it is spelled correctly."
Classic ASP is not enabled by default in IIS 7 and 7.5. It is easy to enable, see http://www.iis.net/learn/application-frameworks/running-classic-asp-applications-on-iis-7-and-iis-8/classic-asp-not-installed-by-default-on-iis
I know a similar question was raised on this in 2009, but I am really baffled by this.
I have a Windows XP development machine which is used for maintenance on a classic ASP web application. IIS 5.1 is the web server.
The problem: some sites serve up classic ASP with no problem, other sites give the "The type of page you have requested is not served because it has been explicitly forbidden. The extension '.asp' may be incorrect. " error in a ASP.Net looking way. Suggesting that asp.dll isn't being used to serve up the pages!? The list of which dll to use with which file extension is the same for both sites. Any new site created appears to have the same issue with serving cASP.
If IIS was consistently failing to server cASP on all sites I would be looking at common configuration, but as it's working on a some and not others I am utterly baffled.
Any help would be appreciated!
Trying to copy a website to a new server as the old one is dying. :(
I tried copying over the files and setting it up manually, but some specific user accounts needed to be used and the guy who set all this up left the company nearly 5 years ago. And is even worse at documentation than I am.
Anyway, at that point the ASP pages were serving, but getting errors. Ok, fine... I went back and exported the configuration from the old server (lucky that worked at all) and created a new website from that config on the new server. On the new website, from the config file, the ASP pages are giving 404 errors.
The Active Server Pages extension is enabled, and I can actually get the asp pages to serve from another website on the server... so I'm thinking it's something at the website level. No idea what though.
Any ideas?
Back when I was doing classic ASP development we used Parent Paths. This is at the top of your ASP file you'll see something like;
<!--#include file="../../resource/includes/MSSQLconnection.asp"-->
This isn't enabled by default in IIS. It may not be answer but worth looking at. But was a long time ago now.
Hope this helps,
Mike
404 is a file not found error.
Start by checking you can access a 'hello world' HTML file in the folder using http: //localhost/path/toyour/HelloWorldFile.htm
Hello World
is all you need in the file = you don't need to bother with any HTML markup to test what we're interested in.
This will check that your virtual directories, application settings etc are correct before you move on to the Active Server Page settings.
Once you've got your paths sorted out and you know you are looking for your application in the correct place move on to a 'hello world' ASP file
<%="Hello World"%>
is all you need in that file!
You ask about settings in IIS which will stop ASP from working. These come to mind as the most obvious.
Depending on the OS (or more specifically the IIS version) you may also need to activate ASP pages.
These instructions from msdn cover Windows 2003 (IIS6) and Windows 2008(IIS 7.x)
If you can get your hello world script working you can move on to debugging your application.
It will be a great help when debugging the application if you can see what's going wrong so I recommend that you turn off friendly error messages if you are using Internet Explorer. Also set IIS to pass error messages on to the browser
see:
http: //learn.iis.net/page.aspx/564/classic-asp-script-error-messages-no-longer-shown-in-web-browser-by-default/ --excuse the link formatting but SO's newbies can't post more than 2 hyperlinks in a message was getting in the way of me trying to be helpful and earning enough rep to post more!
(that may only be relevant to IIS 7.x I don't have an IIS6 installation lying around to refresh my memory.
Make sure you are browsing your application on the server using http: //localhost - this should ensure you see any errors
Good luck
Good Morning,
I was having serious problems regarding this website.
What happens is everyytime I try to open a .shtml page in the site it always has an error "The Page Cannot Be Found" but this is highly unlikely since I already all have the resources in my local pc and already did a virtual directory for the entire site. Can you please tell me what's the problem? i've checked all the codes and they're constructed just fine.
If you're attempting to view the page in Internet Explorer then I recommend turning off friendly HTTP error messages in the advanced settings. Disabling the setting may result in more verbose error messages, especially if it's an HTTP/500.
This is not actually an ASP problem. .shtml files are handled by the server-side include ISAPI application extension.
In Web service Extensions folder under the server icon in IIS manager, ensure that Server Sice Includes is set to "Allowed".