IIS 7 & IIS 8
IIS7 Custom 500.asp page and GetLastError not working
Last post May 02, 2012 03:21 PM by ashrael
Aug 30, 2009 09:49 PM|LINK
I cant, when i try it i get a.. lock violation ;(
Aug 31, 2009 01:39 PM|LINK
the escy way to do it...
Go to Errors list
Now add new error called 500.100
Set it to exceute and add the patch: like /error/error.asp
now you will get your own error file, and server will exceute it..
and Server.GetLastError() works :o)
Aug 31, 2009 06:21 PM|LINK
Editing specific errors does not work for me. I end up with blank emails. The only thing that seems to work for me is "Edit Feature Settings".
It's properties box is somewhat similar to the specific error properties box, but it actually works.
Thank you again AminaG
Sep 03, 2010 09:59 PM|LINK
Is there a specific bug documented for this with Microsoft somewhere? I searched support KB and haven't found anything. It makes it difficult to determine if it is a rumor of a bug, if there is a fix, etc. I am experiencing the same issue -- that is,
no information in the ASPError object returned by Server.GetLastError in a classic asp error handler assigned to handle the 500 status error. I am not using the default error page accessible within feature settings because since it appears to be a work around
for a bug with the GetLastError call when the error handler page, with Execute Url option set for the 500 status. The error handler code was not changed when moved form the IIS6 server to the IIS7.5 server but the functionality changed (the error information
was no longer included in the report). The application pool mode was changed to integrated pipeline-- although I don't know if the execution pipeline mode even impacts classic asp execution much. Any information would be appreciated (beyond assigning the
default error page option).
Feb 10, 2012 10:24 AM|LINK
This was the solution!! 500.100 filter error!
Thank you very much!
May 02, 2012 03:21 PM|LINK
If you receive a lock violation error when trying to modify "Error Pages: Edit Feature Settings....", open the file %windir%\System32\inetsrv\config\applicationHost.config. (If having problems opening the file, run Notepad as Administrator and you should
be able to open it.)
Save, and the lock problem will go away :)