Back in January 2009, I wrote an article: The Importance of Reporting the first Error, which talked about why it is important to report errors, but especially the first error.
After dealing with a number of recent support cases where it came to light during the course of the support case that there had been errors in the past that were not reported, I wanted to cover the subject again.
So, I will stand on my soapbox again (you know I need the height) and explain why this is SO IMPORTANT:
While exceptions are not an everyday occurrence, when I hear about users just clicking OK without noting any details and continuing as though nothing has happened it makes me cringe...
Please note that if these steps are followed, we have a much better chance of identifying the root cause of the issue and so log a problem report to get the issue fixed. Also this gives us the chance to fix or restore the data earlier rather than later.
I can get off my soap box now.
Thank you for touching on a subject that is not discussed much. This is applicable for any software application.
It is also imperative that users participate in the Customer Experience Improvement Program (CEIP) to forward those exceptions to Microsoft. Many times errors are not even application related, but possibly an underlying issue with the operating system. Many times when submitting error reports to Microsoft, you will find it surprising that there's already a fix for the problem.
I also recommend system administrators to use the traditional maintenance routines (Check Links and Reconcile) to identify potential issues and fix potential damages prior to resorting to SQL scripting. While Check Links has a habit of removing records without warning, it does a very good job at letting you know what it removed: PRINT THE REPORTS!!
Mariano Gomez, MVP
Support normally suggest only running Check Links when fixing specific issues. Regardless, make sure you have a backup in case it removes records that are valid. I have seen it remove records from 3rd party products as they did not appear as valid records to the Check Links code.
Posting from Mark Polino from DynamicAccounting.net
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.