What the .TLG file is and why -107 happens: The Transaction Log (.TLG) file is QB's journal of every write operation made to the company file. It is used as a recovery mechanism — if QB crashes mid-write, it reads the TLG to undo incomplete transactions. The -107 error appears when the TLG doesn't match the current state of the .QBW — either because the TLG was from a different point in time (after a backup/restore), because the TLG was partially written (from a crash), or because the TLG was somehow replaced by a file with a different date/state. Renaming the TLG forces QB to create a fresh one from the current .QBW state.

Desynced or Corrupted .TLG File

Primary cause — the .TLG file doesn't match the current .QBW. After a backup restore, the .QBW is at the backup's point in time but the .TLG may be from a later (newer) state — they are out of sync. QB detects the mismatch and cannot open the file safely. Renaming the .TLG removes the conflicting file and QB creates a new one.

Partial .TLG Write from Crash or Power Failure

If QB or the system crashed while the .TLG was being written — mid-transaction log entry — the TLG ends up in an invalid state. QB reads the partially written data, finds an inconsistency, and reports -107. The partial write cannot be completed, so renaming and rebuilding is required.

.TLG from Different Company File

If a company file was moved, copied, or renamed and the .TLG from the original location was accidentally left or matched up with the wrong .QBW, QB finds a TLG that doesn't belong to the company file it's trying to open. This causes -107. Renaming the mismatched .TLG and letting QB create the correct one resolves it.

Damaged .ND File Alongside the .TLG Issue

When the .ND file is also corrupted, it provides QB with the wrong server/path information for the company file. Combined with a TLG issue, this makes QB report -107 because it can't locate or match the company file with the transaction log. Renaming both .TLG and .ND together resolves this variant.

Company File Moved Without Moving the .TLG

If the .QBW file was moved to a new folder but the .TLG was left behind in the old location, QB looks for the .TLG in the new location, can't find a matching one, and creates a new (empty) .TLG — but if an old .TLG is somehow picked up, the mismatch causes -107. Always move .QBW, .TLG, and .ND together as a set.

Outdated QB Version or Damaged Installation

An outdated QB maintenance release may have a bug in TLG reading that newer releases fix. A damaged QB installation can misread valid TLG data and report -107. Updating QB and running the Install Diagnostic Tool addresses this variant.

METHOD 1 Rename .TLG (and .ND) + QBDSM Scan -107-specific — resolves most cases

METHOD 2 Run QuickBooks File Doctor Underlying file or network damage

METHOD 3 Open Sample File Test + Verify/Rebuild Diagnose whether company file or QB installation is damaged

METHOD 4 Copy File to Local Drive + Check Folder Permissions Network path or permissions contributing to -107

METHOD 5 Restore from Backup + Update QB All above tried — .QBW data may have underlying damage

Why does restoring a backup cause Error 6000, 107?

When you restore a .QBB backup, the restored .QBW goes back to the state it was in at backup time. But the .TLG file in the company file folder may still be from a later point — it was written after the backup was made. QB tries to open the restored .QBW using the newer .TLG and finds the data states don't match. This triggers -107. The fix is always to rename the .TLG to .OLD immediately after restoring from backup — before trying to open the restored file. QBDSM then creates a fresh .TLG that matches the restored .QBW's state exactly.

Will renaming the .TLG cause any data loss?

Renaming the .TLG file itself causes no data loss from your company file. Your accounting data — transactions, payroll records, invoices, reports — all lives in the .QBW file. The .TLG only records the log of write operations as a recovery mechanism. When you rename the .TLG and QB creates a new one, the new .TLG starts fresh from the current .QBW state. The only risk is if the .TLG contained transactions from an incomplete write (from a crash) that weren't yet fully committed to the .QBW — in that edge case, those uncommitted transactions wouldn't be recoverable. Run Verify Data after the rename to check for any data inconsistencies.

What's the difference between renaming from the server vs a workstation?

Always rename the .TLG (and .ND) from the computer that is directly hosting the company file — the server. The .TLG is a local file on the server in the same folder as the .QBW. If you rename it remotely through a network share, the rename may not complete cleanly, and the network path itself could be contributing to the -107 error. After renaming, also run the QBDSM scan from the server. For single-computer setups (no server), rename directly on that computer.