Member Avatar for DotNetKnight

Hi,

We are currently facing a strange issue.

We are having an error logging functionality that logs errors occurring to a database.

A scenario occurs where there is an error occurring in the application, custom error page comes up.

When looked in the database for error description error is not logged at all.

However, when the Custom error mode is set to Off and a save is given to the web.config file the error no more occurs and the application works all fine.

In short, Error disappears on just opening and saving the web.config file.

What might be actually causing this strange issue?

  • 4 Contributors
  • 4 Replies
  • 228 Views
  • 3 Months Discussion Span
  • Latest Post Latest Post by migandhi
Member Avatar for aspproject

for logging error you can trace error using try { some code } catch (Exception ex) { } finally { }...in Catch you can show/insert error in error log

Member Avatar for DotNetKnight

Error logging has been done already. We are logging our errors down in a database.
But when queried for error description we were able to see that the error is not getting caught/logged.
Opening and saving the web.config alone is rectifying the issue.

Member Avatar for qwerty1234567

We are facing the same issue.
OPENING ANS CLOSING OF THE WEB.CONFIG FILE AT WHICH POINT OF TIME RESOLVES THIS ISSUE?!

Member Avatar for migandhi

http://msdn.microsoft.com/en-us/library/ms228058.aspx

Any changes to the web.config will make the application to restart..

If you have changes made to the web.config the application may restart..

So when the application is restarted the error goes..

So in one of the possible cases this error goes on application restart
and not actually on
opening and saving of web.config

This may possibly give you some hint ..

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.