Adding a checkbox is not a problem. However this won't help that much. The "500 internal server error" is the error that we get in the header, not within the page. The page itself contains some info (like the ODBC connection...) BUT also a lot of scripting (at least that's how IIS sends it back), so what should we do with that? The %e parameter will show the "500 error".
I'm not sure what exactly you're expecting from that "checkbox" Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow Sent: Tuesday, July 05, 2005 2:45 PM To: [email protected] Subject: Re: [SA-list] "500 Internal Server Error" Can you make a check box just like IE has to use friendly http error messages (500 internal server error) or not (Microsoft Odbc Connection blah blah blah)? Salive is such a great product I guess I am just spoiled by not having to jump in and fix any glitches. The only time we need manual intervention is if some tech screwed something up by manual intervention. Or of course in the event of a complete server meltdown (hardware problem or hard drive crash/corruption). Thanks to Server's Alive I do not have to run into the office (or VPN) at 10:00 at night to fix errors. This is truly a great product and if this one item remains unchanged I guess I can live with having to fix one problem manually. Thank you in advance for your consideration however. Dirk Bulinckx wrote: >No this can be done. >When we request a page from a webserver we get the status back (200 OK, 404 >Page not Found , 500 Internal Server Error). When it's NOT "200 OK" we >won't check the content of that page. And what you're looking for is >probably within the page that is received. > > >Dirk. > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf >Of Jason Passow >Sent: Friday, July 01, 2005 11:15 PM >To: [email protected] >Subject: [SA-list] "500 Internal Server Error" > >I have a wish for Server's Alive. I have a web page that occasionally >cannot communicate with my ODBC connection. The connection works and >when I test it within server's alive using the comODBC add on everything >works. The only solution I have is to reboot the server. The problem >is it returns a 500 internal server error. If I turn off friendly http >error messages in Internet Explorer I am able to distinguish between >someone having the database locked or a corrupt database or the odbc >connection going down. Not all Internal Server Error 500 errors require >a reboot. So Is there any way you can show me the non-friendly http >error message so that I can reboot the server at the appropriate time by >looking at the additional info field. > >If I can do it manually I know you can do it programatically. Thank >you for your consideration of the issue. > > > -- Jason Passow Mississippi Welders Supply [EMAIL PROTECTED] ph: (507) 494-5178 fax: (507) 454-8104 ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive ------------------------- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
