Error logs in a DotNetNuke (DNN) site are filling up with errors like that of below. Are these important? They appear to be 404 related, but why would they be causing a general exception as 404s are being handled by iFinity Url Master. Is there a way in DNN to stop reporting on them?
General Exception
AssemblyVersion: 6.2.0
UserID: -1
UserName:
ActiveTabID: 678
ActiveTabName: 404
RawURL: /Portals/Portals/0/favicon.ico
AbsoluteURL: /404.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: b546f73a-6e44-48d2-9c6e-6bddc70c9ff4
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method:
StackTrace:
Message: System.Exception: Unhandled Error:
These errors can’t be avoided without modification to the DotNetNuke core.
Basically what happens is that the Url Master module handles the 404 error and clears it, but the DNN exception handling still picks the error up and logs it.
This has been logged in the DotNetNuke gemini bug tracking system but not fixed as yet. It’s mentioned in the release notes section of the Url Master install.
As long as your 404 error process is working OK, then there is nothing to worry about.
Exception Module still logs error if error has been cleared