![]() One of the improvements that Intuit has made to the QBWin.log is better event tracking, and performance measures, associated with user operations. Every once in a while I get an email notice that a revised KBA has been posted on a specific topic. New KBA (knowledge based articles) are being added all the time to deal with problems, and Intuit has in fact started posting ‘we don’t know, but we will let you know, when we do’ KBAs. Over the last several years Intuit started improving the quality, quantity and access to technical support documents built around error messages within the QBWin.log file. For years information recorded in the log was cryptic and required knowledge of C++ and Sybase error codes, even such knowledge did not assure a complete understanding since Intuit formulated many of their own error codes. While the log file was initially intended to be viewed (and perhaps emailed) to Intuit Technical Support personnel to assist them in diagnosing problems or data-issues, it is growing useful for a number of other purposes as well. This could be the result of Intuit developing an understanding that more and more QuickBooks ProAdvisors are reading and interpreting these logs when QuickBooks crashes, the Verify Fails, or the Rebuild doesn’t resolve a problem.Ī QBWin.log file is generated each time QuickBooks is started. Recently Intuit began releasing QuickBooks ‘maintenance updates’ that are improving and supplementing the information contained within these log files. There is more to the QBWin.log file than just the Verify and Rebuild utility results. This article is the first covering various procedures for evaluating and improving QuickBooks performance. On the other hand, you may be forced to perform complex evaluation procedures to determine the source of bottlenecks or application related problems. You might find that a network hub is going bad, or that someone is attempting to use QuickBooks on an undersized computer that is already taxed by too little resources. The Company data-file can be one source of performance issues, and the operating environment (computer equipment) can also be the cause of poor performance.ĭiagnosing performance problems can be complex or simple. Performance issues range from Network problems, to Server issues, QuickBooks application problems, and yes, User issues. A multitude of things can cause performance problems, and of course, users have their own 'definitions' for what they think is 'poor performance'. There’s a checkbox setting specific to this error, Force 6130 Fix, that should be checked if a single pass of the tool doesn’t allow the company file to be opened without error.All too often QuickBooks ProAdvisors are called to 'evaluate' and 'fix' problems with QuickBooks performance. Users experiencing error code -6130, 0 may need to run the tool a second time to resolve this error. Intuit has a step-by-step guide to installing and running the Company File Diagnostic Tool. There’s also the possibility that your company file has damage that the tool is unable to detect. If the tool doesn’t find a problem and you still can’t open the company file, your problem may be caused by something other than company file data damage, such as your computer configuration. If the tool identifies a problem and can’t fix it, you can either restore from a backup or investigate other data recovery options. The tool identifies a problem but can’t fix it.The tool identifies and repairs the problem that prevented you from opening the company file in QuickBooks.There are 3 possible outcomes from running the Company File Diagnostic Tool: The program only works on company files (.qbw) from QuickBooks 2006 or newer. The tool is a program that you can download from Intuit, install on the same computer where the company file is located, and run. Intuit’s QuickBooks Company File Diagostic Tool is designed to diagnose and repair problems that prevent a company file from opening.
0 Comments
Leave a Reply. |