TECHNO TOPIC: Rare QuickBooks Errors Encountered



Comments (4)

Comment Feed

Verify Data causing problems?

A client recently was told by Intuit support (not ProAdvisor level support) that they shouldn't run Verify Data unless they have known errors as running the Verify Data causes problems if there aren't any to begin with. This doesn't make sense to me, what do you think?
In this case, errors were found and Rebuild couldn't fix them so the client ended up sending their data file for repair with Intuit - a serious financial hardship for daily operations.

Karen Cook more than 2 years ago

Your Client probably misunderstood.....

Intuit has said for years that you should NOT run the REBUILD Utility unless there are known errors, that there is the possibility of corruption by doing so. But I have never heard anyone from Intuit (or seen any technical support information) on Not Running Verify.

Verify (in fact 'full verify') is a normal integrated part of the Internal QuickBooks process 'by default', you must manually option to not verify the data and Intuit emphasizes the importance of regular back-ups, even by default prompting you to back-up (including verify).

I think your client must simply have misunderstood.

As far as not running Rebuild, there are other times it should NOT be used. We know for example that if you have 'encryption errors', the Rebuild utility can actually cause them to increase and/or spread to other segments of encrypted data.

There are lots of situations where the QuickBooks Rebuild utility can not resolve corruption, but many of those circumstances can be resolved if the user can read and properly interpret the QBWin.log, and then make the necessary 'manual corrections' to affected transactions or list records. In those cases a Rebuild may not even be necessary after the corrections are made, and when the Verify is run, the utility ends cleanly.

The issues discussed in this article deal with some of the most ominous forms of corruption, structural integrity loss, but fortunately such problems are rare given the stability of the actual database structure itself.

Thanks for your comments, and thanks for reading Intuitive Accountant.

Murph more than 2 years ago

Running Rebuild Regularly (i.e. weekly)

I have advised some QBES clients with 5- 10 users to regularly run rebuild (weekly) to avoid data corruption. Is this a bad idea. Should they just run verify weekly? Is this the same verify that gets run with automatic full back ups?

Steve Bradely more than 2 years ago

Never Run Rebuild without a specific Reason

You really should NOT run the rebuild reason without having a very specific reason, and that reason should usually take the form of a 'Verify' that does not end with the message "QuickBooks found no problems with your data', of a QBWin.log file that clearly shows data errors that can in fact be corrected by use of Rebuild.

Many QuickBooks errors can not be corrected using the Rebuild Utility, the values that are mismatched are not computational in nature, they are user defined errors. In these cases the fix is also manual (or comes from a source other than Rebuild).

In some cases Rebuild can actually damage your data, for example the 'encryption/decryption' errors that have become common in QB 2013 and 2014 can be made significantly worse by using Rebuild. A few corruption errors can quickly turn into 100's via a Rebuild in some cases.

The Verify utility should be run regularly, and typically as part of an 'internal QuickBooks Backup' (with the option for full verification). If this fails to complete, then you are ready to start the process of diagnosing what is wrong with the data using both the Verify Utility and QBWin.log file as your references. Only when you are certain you should in fact 'run Rebuild', should you do so.

Best of luck,

Murph more than 2 years ago

a small ad separator
IA Newsletter BL
a small ad separator
a small ad separator
a small ad separator
a small ad separator
Built with Metro Publisher™