ASP.NET: Errors not viewable despite proper configuration?

The error is a . NET framework error so it finds the app, but there is a configuration error. What you could do is add some event logging code in APplication_Error handler in global.

Asax to trap these errors, or turn on health monitoring ( healthMonitoring enabled="true ), which by default will log ASP. NET framework errors to the event log HTH.

The error is a . NET framework error so it finds the app, but there is a configuration error. What you could do is add some event logging code in APplication_Error handler in global.

Asax to trap these errors, or turn on health monitoring (), which by default will log ASP. NET framework errors to the event log. HTH.

I tried both, but neither worked. Thanks for the input, though. – Helgi Hrafn Gunnarsson Mar 1 at 18:55.

Never got this working until I changed the application from a "sub-application" (I don't know the proper terminology) to an independent website with its own hostname. ASP. NET works in mysterious ways.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.