Detailed 500 error message ASP IIS 7 5

Question

IIS 7 5   2008rc2  classic asp  500 error msg      The page cannot be displayed because an internal server error has occurred    I need to know how to configure IIS to get a more detailed error  I ve tried setting to true all of debugging options in the ASP configuration  But that didn t work  Can anyone help me

User · Answer

Fot people who have tried EVERYTHING and just CANNOT get the error details to show  like me  it s a good idea to check the different levels of configuration  I have a config file on Website level and on Application level  inside the website  check both  Also  as it turned out  I had Detailed Errors disabled on the highest node in IIS  just underneath Start Page  it has the name that is the same as the webservers computername   Check the Error Pages there

User · Answer

try setting the value of the  existingResponse  httpErrors attribute to  PassThrough    Mine was set at  Replace  which was causing the YSOD not to display    lt httpErrors errorMode  Detailed  existingResponse  PassThrough  gt

User · Answer

One thing nobody s mentioned is as a very quick and temporary fix  you can view the error on the localhost of that web server

User · Answer

If you re on a remote server you can configure your web config file like so    lt configuration gt   lt system webServer gt       lt httpErrors errorMode  Detailed    gt       lt asp scriptErrorSentToBrowser  true   gt   lt  system webServer gt   lt system web gt       lt customErrors mode  Off   gt       lt compilation debug  true   gt   lt  system web gt

User · Answer

Double click  ASP  in the site s Home screen in IIS admin  expand  Debugging Properties   enable  Send errors to browser   and click  Apply    Under  Error Pages  on the home screen select  500   then  Edit feature settings  and select  Detailed Errors    Note that the same steps apply for IIS 8 0  Windows Server 2012

User · Answer

You may also verify that if you changed your main website folder  c  inetpub wwwroot  to another folder you must give read permission to the IIS IUSRS group in the new folder

User · Answer

TLDR First determine where in the pipeline you re getting the error from  scroll looking for screenshots of something that resembles your error   make changes to get something new  repeat   First determine what error message you are actually seeing   If you are seeing the file located here      SystemDrive  inetpub custerr  500 htm     which generally looks like this        then you know you are seeing the currently configured error page in   IIS    and you do NOT need to change the ASP net customErrors setting  asp error detail setting  or  show friendly http errors  browser setting   You may want to look at the above referenced path instead of trusting my screenshot just in case somebody changed it    Yes  I see the above described error      In this case  you are seeing the setting of  lt httpErrors  or in IIS Manager it s Error Pages --  Edit Feature Settings   The default for this is errorMode DetailedLocalOnly at the server node level  as opposed to the site level  which means that while you will see this configured error page while remote  you should be able to log on locally to the server and see the full error which should look something like this     You should have everything that you need at that point to fix the current error    But I don t see the detailed error even browsing on the server   That leaves a couple of possibilities      The browser you are using on the server is configured to use a proxy in its connection settings so it is not being seen as  local   You re not actually browsing to the site you think you are browsing to - this commonly happens when there s a load balancer involved   Do a ping check to see if dns gives you an IP on the server or somewhere else  You re site s httpErrors settings is set for  Custom  only   Change it to  DetailedLocalOnly    However  if you have a configuration error  this may not work since the site level httpErrors is also a configuration item   In that case proceed to  4 The default for httpErrors for all sites is set for  Custom    In this case you need to click on the top level server node in IIS Manager  and not a particular site  and change the httpErrors settings there to DetailedLocalOnly   If this is an internal server and you re not worried about divulging sensitive information  you could also set it to  Detailed  which will allow you to see the error from clients other than the server  You re missing a module on the server like UrlRewrite  this one bites me a lot  and it often gives the generic message regardless of the httpErrors settings      Logging on to the server is not an option for me   Change your site s httpErrors to  Detailed  so you can see it remotely   But if it doesn t work your error might already be a config error  see  3 immediately above   So you might be stuck with  4 or  5 and you re going to need somebody from your server team    I m not seeing the error page described above   I m seeing something different   If you see this          and you expect to see something like this          then you need to change  Send errors to browser  to true in IIS Manager  under Site --  IIS --  ASP --  Debugging Properties  If you see this       or this          you need to disable friendly errors in your browser or use fiddler s webview to look at the actual response vs what your browser chooses to show you   If you see this          then custom errors is working but you don t have a custom error page  of course at this point were talking about  net and not classic asp    You need to change your customErrors tag in your web config to RemoteOnly to view on the server  or Off to view remotely   If you see something that is styled like your site  then custom errors is likely On or RemoteOnly and it s displaying the custom page  Views- Shared- Error cshtml in MVC for example    That said  it is unlikely but possible that somebody changed the pages in IIS for httpErrors so see the first section on that

User · Answer

After trying Vaclav s and Alex s answer  I still had to disable  Show friendly HTTP error messages  in IE

User · Answer

In web config under    lt system webServer gt    replace  or add  the line   lt httpErrors errorMode  Detailed  gt  lt  httpErrors gt    with   lt httpErrors existingResponse  PassThrough  errorMode  Detailed  gt  lt  httpErrors gt    This is because by default IIS7 intercepts HTTP status codes such as 4xx and 5xx generated by applications further up the pipeline   Next  enable  Send Errors to Browser  under the  ASP  section  and  under  Error Pages   Edit Feature Settings   select  Detailed errors    Also  give Write permissions on the website folder to the IIS IUSRS builtin group

User · Answer

I have come to the same problem and fixed the same way as Alex K   So if  Send Errors To Browser  is not working set also this   Error Pages -  500 -  Edit Feature Settings -   Detailed Errors     Also note that if the content of the error page sent back is quite short and you re using IE  IE will happily ignore the useful content sent back by the server and show you its own generic error page instead  You can turn this off in IE s options  or use a different browser

User · Answer

Found it   http   blogs iis net ksingla archive 2009 02 16 iis-7-5-updates-to-custom-errors-and-compression aspx  run cmd as administrator  go to your system32 inetsrv folder and execute   appcmd exe set config -section system webServer httpErrors -allowAbsolutePathsWhenDelegated true   Now I can see detailed asp errors

User · Answer

In my case it was permission issue  Open application folder properties - gt  Security tab - gt  Edit - gt  Add  IIS AppPool  DefaultAppPool or any other apppool   if use ApplicationPoolIdentity option  IUSRS IIS IUSRS

User · Answer

If you run the browser in the server and test your url of the project with the local ip you have received all errors of that project without a generally error page for example 500 error page

[asp-classic] Detailed 500 error message, ASP + IIS 7.5

Examples related to asp-classic

Examples related to error-handling

Examples related to iis-7.5