• Skip to primary navigation
  • Skip to main content

QBGarage.com

The QuickBooks Specialists

  • Home
  • Blog
  • KnowledgeBase
  • Company
  • Show Search
Hide Search
You are here: Home / Archives for TLG file

TLG file

How Can I Improve the Performance of QuickBooks?

Chief Mechanic · September 12, 2010 ·

QuickBooks is a complex program that processes a lot of data.  As data is added to a QuickBooks company file (.qbw), loading and processing times increase.  Within the program, slower processing is usually seen when performing tasks that involve the entire company file, such as running utilities or preparing reports.  Since QuickBooks is typically used every day over a period of years, it’s highly likely that at some point you’ll find a need to improve performance.

There’s no single solution that will improve performance in every circumstance, but there are a series of steps you can take that together will have a dramatic impact on QuickBooks performance.  We’re ignoring the “common sense” recommendations of “buy a faster computer with more memory” or “upgrade to the latest version/update to the latest release.”  Spending money on new or upgraded hardware and not running outdated software will improve performance.

We recommend that you:

  1. Close your company file before exiting QuickBooks and reduce to a minimum the amount of windows that do open once you open your company file.  This will dramatically reduce the time it takes to load QuickBooks, which is one way users measure performance, but it won’t have any impact on performance while working in the program itself.
  2. Perform a manual, verified backup on a regular basis.  QuickBooks maintains a transaction log file (.tlg) that is used in conjunction with its manual, verified backup routine.  This .tlg file grows and can often become bigger than a company file (.qbw) itself.  A manual, verified backup reduces the .tlg file size and improves performance.  Scheduled QuickBooks backups don’t count, nor do other backup routines that you happen to use.  When the .tlg file exceeds 25% of the size of the company file (.qbw) size, it’s time to do a manual, verified backup.  Remember that the primary purpose of this step is to reduce the .tlg file size, not to back up data.
  3. Reduce your DB file fragments if they’re too high.  DB file fragments represent the degree to which pieces of your QuickBooks company file (.qbw) are scattered over your hard disk.  The more fragments you have, the lower your performance will be.  For most organizations, DB file fragments in the single digits are reasonable.  Organizations running Terminal Services will see more DB file fragments, into the low double digits, and that’s reasonable.  If your DB file fragments exceed those levels, convert your company file (.qbw) into a portable file, and then convert that portable file into a company file (.qbw).  That conversion routine will reduce DB file fragments and improve performance.
  4. Clear the queues for forms to be printed.  Large numbers of forms with the To be printed flag set can degrade performance.  The most common example of this problem is a large number of invoices that are in the print queue.  Remove these invoices from the print queue and performance will improve.
  5. Run the clean up utility to reduce your company file’s overall size.  For QuickBooks Pro and Premier, Intuit recommends keeping data files under 100 Mb for reasonable performance.  The clean up utility can remove stale list items and consolidate closed transactions, thereby shrinking file size and improving performance.
  6. Avoid excessive use of sub-accounts, sub-items, and Jobs, which are effectively sub-customers.  Relatively speaking, a sub-account requires more processing than a top-level account, so the more sub-level list entries you create, the slower your performance will be.  The performance penalty is small, so don’t let this fact alone discourage your use of sub-level entries when necessary.  Some organizations have used sub-level list entries excessively, when other QuickBooks features would have been better suited to the purpose.
  7. Stop using Google Desktop.  Google Desktop can only index a QuickBooks company file (.qbw) when that file is open.  Google Desktop indexing routines consume processing and memory resources, leaving fewer of these resources available to QuickBooks.  That will degrade performance.  Uninstalling Google Deskop will improve performance.
  8. Consider an upgrade to Enterprise Solutions.  The database engine behind Enterprise Solutions is more robust and is capable of handling larger company files at reasonable performance levels.  If your business has grown and your QuickBooks company file can’t be cleaned up to where it offers reasonable performance, Enterprise Solutions will provide improved performance.
  9. Investigate network issues if QuickBooks is installed on a network.  For example, mismatched network interface card (NIC) settings can significantly reduce network performance.  If QuickBooks is the primary program that’s used over the network, this network configuration issue can appear to be a QuickBooks performance problem.

For some of these recommendations, the impact will be significant.  For others, it may be imperceptible.  What works or doesn’t work will be heavily dependent on your own configuration.

Intuit describes some of these recommendations in this knowledge base article.

Vote This Post DownVote This Post Up (+1 rating, 1 votes)
Loading...

What Does Error Code 80070057 Mean?

Chief Mechanic · September 10, 2010 ·

According to Intuit, Error Code 80070057 has several variations, each of which has different causes and solutions.  Some variations remain unresolved. Interestingly, before converting our KnowledgeBase to the present format, our article on this error code was our most viewed article by a factor of more than 2 to 1.  That’s a good indicator of the relative occurrence of the error among QuickBooks users.

To attempt to resolve the error, match your exact error with the description below and follow the troubleshooting steps for that specific error.

Variation 1

Error Code 80070057: “There was an unexpected error reported while trying to run QuickBooks” is an error that has multiple possible causes.  The possible causes include:

  • your company file (.qbw) is damaged and you were attempting to backup or create a portable file (.qbm)
  • your QuickBooks installation is damaged
  • you were attempting to open a portable file (.qbm) but QuickBooks wasn’t open
  • the QuickBooks company file extension was changed or is the wrong type

The steps to resolve this error can include reviewing the extension of your company file, verifying your company file, repairing your QuickBooks installation, or re-installing QuickBooks.

To follow the troubleshooting steps to this variation of the 80070057 error, consult this Intuit knowledge base article.

Variation 2

Error: “80070057 the parameter is incorrect” and “You do not have sufficient permissions to delete files…”

There are 2 known causes for this error:

  • a user attempted to launch QuickBooks by double-clicking on a company file (.qbw) instead of launching QuickBooks first
  • by default BitDefender is blocking certain ports that QuickBooks uses to exchange data

To follow the troubleshooting steps to resolve this variation of the 80070057 error, consult this Intuit knowledge base article.

Variation 3

Error: “80070057, the parameter is incorrect. There was an unexpected error reported while trying to run QuickBooks with company file [path and name].”

Unfortunately, Intuit hasn’t identified a resolution to this particular variation of the 80070057 error.  Two suggestions appear in this Intuit knowledge base article: restart all computers running QuickBooks or uninstall/reinstall QuickBooks.

Variation 4

Error: “80070057: parameter is incorrect” when clicking on a QBB, QBM, QBW, ND, or TLG file from a Google Search Timeline.

This is yet another variation of the 80070057 error, and unfortunately Intuit hasn’t identified a possible resolution at this time.  The error is discussed is this Intuit knowledge base article as well as this one.

See our related article on Error Code -6150, -1006 for more information.

Vote This Post DownVote This Post Up (+2 rating, 4 votes)
Loading...

What Does Error Code -6190, -816 Mean?

Chief Mechanic · September 10, 2010 ·

According to Intuit, Error Code -6190, -816: “QuickBooks was unable to open the file [pathfilename] on the host” is an error that can occur when running QuickBooks in multi-user mode on a Linux server.  It’s caused because the company file (a file with an extension of .qbw) doesn’t match the transaction log (a file with an extension of .tlg).  If a company file without the matching transaction log file was updated on another computer and copied back to the server, the two files wouldn’t match.

The simple fix is to locate the mismatched transaction log file (.tlg) and delete it.  QuickBooks will automatically re-create it on startup.

It’s a good idea to know the folder in which your QuickBooks company file and associated transaction log file are located.  Once you’ve resolved this error and can successfully launch QuickBooks, you can confirm the File Information for that company by pressing F2 while QuickBooks is running.  Doing so will display the Product Information window.  The Location field shows the path to that company file.

QuickBooks Premier 2009 Product Information  Location

For more information on resolving Error Code -6190, -816, consult this Intuit knowledge base article.

See our related article on Error Code -6190, -82 for more information.

Vote This Post DownVote This Post Up (+4 rating, 6 votes)
Loading...

What Does Error Code -6190, -82 Mean?

Chief Mechanic · September 10, 2010 ·

According to Intuit, Error Code -6190, -82: “QuickBooks was unable to open the file [pathfilename] on the host” is an error that can occur when running QuickBooks in multi-user mode on Windows Server.  It’s caused because the company file (a file with an extension of .qbw) doesn’t match the transaction log (a file with an extension of .tlg).  If a company file without the matching transaction log file was updated on another computer and copied back to the server, the two files wouldn’t match.

The simple fix is to locate the mismatched transaction log file (.tlg) and delete it.  QuickBooks will automatically re-create it on startup.

It’s a good idea to know the folder in which your QuickBooks company file and associated transaction log file are located.  Once you’ve resolved this error and can successfully launch QuickBooks, you can confirm the File Information for that company by pressing F2 while QuickBooks is running.  Doing so will display the Product Information window.  The Location field shows the path to that company file.

QuickBooks Premier 2009 Product Information  Location

For more information on resolving Error Code -6190, -82, consult this Intuit knowledge base article.

See our related article on Error Code -6190, -816 for more information.

Vote This Post DownVote This Post Up (No Ratings Yet)
Loading...

What Does Error Code -6073, -816 Mean?

Chief Mechanic · September 10, 2010 ·

According to Intuit, Error Code -6073, -816: “QuickBooks is unable to open this company file” is an error that has multiple possible causes.  The possible causes include:

  • multiple computers have hosting turned on instead of only 1
  • different releases of QuickBooks on the server and the affected workstation
  • insufficient file permissions
  • the Database Manager service is not running
  • the network data file (.nd) is damaged, missing, or marked as hidden
  • the transaction log file (.tlg) is marked as hidden
  • security software (e. g., a firewall) is blocking network traffic
  • other software is currently scanning the QuickBooks company file
  • QuickBooks is attempting to run a scheduled backup while the company file is in use
  • the company file (.qbw) is damaged

A screenshot of the actual error appears below:

QuickBooks Premier 2007 Error Code -6073, -816

There are a number of troubleshooting steps to resolve this error that are discussed in detail in the Intuit knowledge base article linked below.  Before proceeding to those steps, insure that all computers in your QuickBooks installation have been updated to the latest QuickBooks release.  To verify the version and release of QuickBooks, press F2 while QuickBooks is running to display the Product Information window.  The Product field shows the version and release at the top left of the window.  In the example below, Premier Accountant Edition 2009 is the version and R3P is the release.  Complete this step on each computer in your multiuser setup.

QuickBooks Premier 2009 Product Information Release

To follow the troubleshooting steps to resolve Error Code -6073, -816, consult this Intuit knowledge base article.

[Update: Unfortunately, it appears Intuit has removed that article, so the link is dead.]

See our related articles on Error Code -6190, -83 and Error Code -6138, -82 for more information.

Vote This Post DownVote This Post Up (No Ratings Yet)
Loading...
  • Go to page 1
  • Go to page 2
  • Go to Next Page »

Accounting

  • Financial Accounting Standards Board

Developer

  • Intuit Developer Network Forums
  • qbXML Onscreen Reference

Intuit

  • Enterprise Solutions
  • Intuit
  • Intuit Marketplace
  • QuickBooks
  • QuickBooks Online Community

QBGarage.com

Copyright © 2008–2023 QBGarage.com · Privacy · Terms & Conditions · Site Help