locked
500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed. RRS feed

  • Question

  • User349326525 posted

    I migrated over to server 2008 (iis 7.5) from server 2003 (iis 6.0) and I am battling the 500 - Internal server error.

    I have under the Debugging Properties in the asp section, everything set to True.  However, still on the client machine I receive the above error message instead of the true error message.  Running the page on the server itself shows the correct error message, but on my workstation, it does not.  This is a large pain to have to run the page on the server to get the error message, back to my workstation to change the code, then back to the server to test.

    I'm not sure what else needs to be enabled to see the error message on my workstation.  I have friently http error messages turned off (have for years).

    any ideas of what I am missing?

    Tuesday, June 21, 2011 1:04 PM

Answers

  • User-1672167363 posted

    Hello,

    Could you check this http://learn.iis.net/page.aspx/267/how-to-use-http-detailed-errors-in-iis-70/ page

    for the Work Flow for how messages are handled for Client and Server.

    Please check the Figure 3 and the notes # 1 and # 2 for the over-ride settings and the Table description.

    I think if you use the over-ride settings you will get the information you need?

    Martin

     

     

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, June 22, 2011 12:20 PM

All replies

  • User-1672167363 posted

    Hello,

    Have you checked this http://learn.iis.net/page.aspx/565/using-failed-request-tracing-to-troubleshoot-classic-asp-errors/ guide?

    Martin

     

    Tuesday, June 21, 2011 1:25 PM
  • User349326525 posted

    That looks like it would do what I want, but I'm really just looking for the error message to display, and nothing else.  just like iis 6.0 had it, and just like my server displays it currently.  Example would be :

    Microsoft VBScript runtime

    error '800a000d'

    Type mismatch: 'dfg'

    /test.asp, line 3

    I just want that displayed, not any of the tracing options.  If, however, I have to jump through hoops to get this error message displayed on my workstation as it is displayed on the server, then I guess I will have to go that route.  Please confirm I have to do what you posted.

    Tuesday, June 21, 2011 1:51 PM
  • User-1672167363 posted

    Hello,

    You can use this as the Alternate http://learn.iis.net/page.aspx/564/classic-asp-script-error-messages-no-longer-shown-in-web-browser-by-default/ 

    which is more like IIS 6.0 and Windows 2003.

    I would suggest you turn it off  Both on a Production Server.

    Martin

     

    Tuesday, June 21, 2011 2:16 PM
  • User349326525 posted
    That is what I am doing so far to display the error message on the server; however, when I enable it for client side debugging, I still get the 500 error.
    Tuesday, June 21, 2011 5:17 PM
  • User-1672167363 posted

    Well in that case Failed Request Tracing and selecting the type 500 and verbose

    and asp maybe be the best option.

    Martin

     

    Wednesday, June 22, 2011 12:23 AM
  • User-470603225 posted

    Could you please advise the full error message that you get on the server? Or please check http://windows2008hosting.asphostportal.com/post/IIS-70-Hosting-ASPHostPortal-Troubleshooting-HTTP-50019-Errors-in-IIS-7-Part-1.aspx.

    Hope it helps!!

    Wednesday, June 22, 2011 1:56 AM
  • User349326525 posted

    Ok.  I have enabled tracing and I can generate the xml file to view, but again, it is on the serve, and I can not see the trace log or the error message on the client, which I must be able to do.

     Basically, I want to view a page and receive the true error, log error, whatever.  I do not want to have to view the page, receive the 500 error, then go to the server and view a log or reproduce the error to see what the message is.

    I have no issues troubleshooting the actual error, I just need to be able to see it without having to go to another PC / Server install.

    Wednesday, June 22, 2011 11:45 AM
  • User-1672167363 posted

    Hello,

    Could you check this http://learn.iis.net/page.aspx/267/how-to-use-http-detailed-errors-in-iis-70/ page

    for the Work Flow for how messages are handled for Client and Server.

    Please check the Figure 3 and the notes # 1 and # 2 for the over-ride settings and the Table description.

    I think if you use the over-ride settings you will get the information you need?

    Martin

     

     

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, June 22, 2011 12:20 PM
  • User349326525 posted

    Thanks for the article.  By reading it, It led me to the solution.  In my site (for my case, I have a test site no one else has access to), I went to Error Pages in IIS, click edit feature settings and then changed it to Detailed errors.  That sends the error message to the client computer.

    Thanks!

    Wednesday, June 22, 2011 12:46 PM