C
cjmwork2
Guest
My IPP uses Plesk7 as their control panel software.
Generally I think that Plesk is pretty good, however I have had a few problems which my IPP have claimed was a limitation of Plesk.
The one that is bugging me at the moment is how difficult it is to debug ASP 500 errors - 'Internal Server Error'.
Rather than give the native IIS error which will give an reasonable attempt at explaining what went wrong - and at what line - Plesk is configured to give a generic error message which gives you no idea what is wrong. Instead, I must download the full Access_logs file - which is usually 50KB+.
If I check the access_logs file I get an indication of the type of error, but still no indication of where the error occurs.
Is there any way to improve on this? Why can't the default IIS error messages (including problem and line no) be displayed?? If there is a good reason for this, why cant an alternative be implemented - something that gives an indication of the problem, where it occurs, and via a means that is easily accessible?
Why, out of interest are the errors listed in the access_logs file, rather than the error_logs file? Why does this file have no extension (eg. .TXT)? It makes it a PITA to open on a windows machine.
I suspect I'm stuck with the status quo, but I live in hope....
cheers
Chris
Generally I think that Plesk is pretty good, however I have had a few problems which my IPP have claimed was a limitation of Plesk.
The one that is bugging me at the moment is how difficult it is to debug ASP 500 errors - 'Internal Server Error'.
Rather than give the native IIS error which will give an reasonable attempt at explaining what went wrong - and at what line - Plesk is configured to give a generic error message which gives you no idea what is wrong. Instead, I must download the full Access_logs file - which is usually 50KB+.
If I check the access_logs file I get an indication of the type of error, but still no indication of where the error occurs.
Is there any way to improve on this? Why can't the default IIS error messages (including problem and line no) be displayed?? If there is a good reason for this, why cant an alternative be implemented - something that gives an indication of the problem, where it occurs, and via a means that is easily accessible?
Why, out of interest are the errors listed in the access_logs file, rather than the error_logs file? Why does this file have no extension (eg. .TXT)? It makes it a PITA to open on a windows machine.
I suspect I'm stuck with the status quo, but I live in hope....
cheers
Chris