According to Intuit, the error code referencing Microsoft’s msvcr80.dll is an error that can occur when running the Rebuild Data utility on a company file (.qbw) that had been converted from an older to a newer version. It indicates that the company file (.qbw) had possible data corruption before the file was converted to the newer version.
The error is accompanied by the following:
QuickBooks has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to us. We will treat this report as confidential and anonymous. To see what data this error report contains, click here.
Clicking on the link to the error report displays:
Error signature AppName: qbw32.exe AppVer: 18.0.4001.606 ModName: msvcr80.dll
If possible, Intuit recommends returning to the file before it was converted to the newer version, repairing the damage, and re-converting to the newer version.
However, if the file had been converted some time ago, this solution isn’t practical.
For more information on this error, consult this Intuit knowledge base article.
(No Ratings Yet)
Loading...
My error displays the above details in event viewer but its not about a file. Its after I have installed QuickBooks 2009/10 Premium (Multi-User) on Windows Server 2008 32 bit version. The Database Manager starts up and runs fine. But the QuickBooks application starts up gives an error messagin stating a problem was detected and windows is looking for a solution then closes.
I am trying to deploy and test out QuickBooks but this problem has affected my progress and I have not been able to resolve it even with all the solutions on the forum
In need of urgent help
Your best bet is to contact Intuit support for the QB 2010 while you’re still covered. Support will end in May. For QB 2009, support for that product is over, so you’ll have to hope that any solution offered applies to both versions. Unfortunately, it’s not practical to attempt to diagnose problems in a network installation of QB via our blog comments, especially if your situation is urgent.