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".
Related
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!
We have a problem under Microsoft IIS. People are not able to request the favicon through the browser. We checked all the coding of the website we are hosting on it and it is all fine. Problem is that the icon file seems to be blocked in general for the outside world:
Icon location: http://www.raakbeleving.nl/favicon.ico (gives 404)
Anybody any clue what could make this happen?
Our hosting provider cannot seem to solve the problem.
Thanks in advance.
See this page for a way to set up the content type in IIS 7.
Here there are a number of additional hints for it..
MS IIS Manager version 1809 includes a MIME type of .ico
**To Clarify the Problem: **
I have my favicon.ico in the root directory of my application which has an alias name of the website. I have run the same html through a number of servers. Each one looks for the favicon.ico, finds it, and uses it.
When you access a website without a favicon.ico, the icon on the browser tab for that site will have a browser default icon. The favicon.ico, when it exists, will replace that tabl icon with a custom one. I have found a lot of sites that discuss how MS IIS does not support favicon.ico.
I've developed a site in modx but after migrating it to the live server if I enter a page that doesn't exist (eg http://mysite.com/index.php?id=5) I'm getting the default IIS error page rather than the page specified in Tools->Configuration->site->Error page
Any idea why this could be happening?
For the record I developed on Apache but am deploying to IIS.
The only thing I can think of is that IIS is over-riding the modX error page somehow.
I know on Apache I can fiddle with the .htaccess file to set ErrorDocument, but I don't know how IIS works.
Perhaps previous SO questions on "custom 404 page on IIS" might give you some clues as to how your system is setup.
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
I have recently inherited a website written in Classic ASP, and am currently trying to get a sense of the state of things. The website is working in production, however the development environment (hosting on a Windows Server 2003 box) produces an HTTP 500 error when you try to navigate to it.
I realize that HTTP 500 errors just mean that an unexpected server error occurred, and that this also is more than likely the ASP code crashing for one reason or another. I have tried numerous browsers (IE, Firefox, and Chrome) but they all have the same amount of information.
Being primiarly an ASP.NET developer I am use to the yellow screen of death which can be configured to show a stack trace.
So my question is, how do I convince IIS and/or Classic ASP to give me a better hint about what is causing the error?
Update:
I should have gone into more detail originally, but here are some of the things I've looked at.
I've looked at the event logs
(Application, Security, System, etc)
and there is nothing relevent there.
I have looked at the IIS access logs
and I see the access attempts, and
just 500 errors. It is even
producing 500 errors on favicon.ico
If you can't find the offending line by turning off "Show friendly HTTP error messages" as Wayne suggested, then try adding "On Error Resume Next" to the code along with response.write statements. I've found with problems like these, you just have to start going line by line through the code until you find the offensive code.
Just out of curiosity, is Active Server Pages set to allowed in the Web Server extensions in IIS on the dev servers?
Have you checked the Application portion of the web server's Event Viewer for error entries?
What alex said, also make sure that you turn off "Show friendly HTTP error messages" in Internet Explorer and then browse to the site; that tends to give you a more specific error message (although still generic compared to ASP.NET's stack trace) along with the line number.
If you have a global.asa file in your web directory, you could rename the file and try loading the favicon.ico file again. If it loads, the problem lies within the global.asa
Clearly an old question, but for what it's worth, if you have access to the development server (direct or remote desktop), you can access the site from there. Localhost requests reveal more debugging information about classic ASP including line numbers.