Last post Feb 11, 2019 06:10 PM by PatriceSc
Feb 11, 2019 12:22 PM|jsshivalik|LINK
In the below code when i set <customErrors mode="Off"/> then i get above error.
<compilation debug="false" targetFramework="4.5"/>
<httpRuntime targetFramework="4.5" maxRequestLength="20480" executionTimeout="1600" />
Feb 11, 2019 01:49 PM|AddWeb Solution|LINK
First, you need to enable and see detailed errors of your web messages, because this is a general message without giving information on what's really happening for security reasons.
With the detailed error, you can locate the real issue here.
Also, if you can run the browser on the server, you get details on the error, because the server recognizes that you are local and shows it to you. Or if you can read the log of the
server using the Event Viewer, you also see the details of your error.
<httpErrors errorMode="Detailed" />
Note: You can avoid the Debug=true. You only need to close the custom errors for a while and get the detailed error page.
Reference: Enabling Windows custom error messaging in Go Daddy's help
Also, this can help: How to enable the detailed error messages (from
Feb 11, 2019 04:22 PM|DA924|LINK
The 500 error means the Web program through a .NET exception that was unhandled. Yo need to use a try/catch to expose the exception.
Feb 11, 2019 06:10 PM|PatriceSc|LINK
Or by default, exception details should go to the Windows Event log (Application). I hardly see why switching from On to Off would cause an error but as always with errors it's best to just see which error you have rather than trying to guess...