QuickBooks Error Code C272

Let’s Dive in to see…

How to Fix QuickBooks Error Code C=272

Schedule a call to fix QuickBooks Errors
QuickBooks Payroll Error PS060

QuickBooks Database Error · C Series

How to Fix QuickBooks Error C=272

QuickBooks displays: "QuickBooks Error C=272" when running Verify Data, Rebuild Data, opening a memorised report, or during a company file upgrade.

Error C=272 is part of the C-series database error group — it occurs when QB's internal data utility encounters a database record outside its expected range, or when a memorised report from an older QB version did not convert properly. At QuickFix Bookkeeping, the 60-second sample company file test tells you immediately whether to fix the data or fix the installation.

The QuickFix Bookkeeping Distinction — The Sample Company File Test

C=272 can originate from your company file or from QB's installation / Windows compatibility settings. One test tells you which — so you skip straight to the right fix.

How to Run the Test (60 seconds)

Hold Ctrl and double-click the QuickBooks icon. Release Ctrl when the No Company Open window appears. Click Open a sample company → choose any sample file. Now reproduce the action that produced C=272 — run Verify Data, or open the memorised report that failed.

What the Result Tells You

C=272 clears on sample file → the problem is your company file's data. Run Verify + Rebuild. If Rebuild cannot fix it, restore from a pre-corruption backup.

C=272 persists on sample file → the problem is QB's installation or Windows compatibility mode. Disable compatibility mode on both the QB shortcut AND QBW32.EXE.

The memorised report specific case: If C=272 appears only when you open or run a specific memorised report — not during Verify Data and not on the sample file — the cause is a report created in an older QB version that did not convert correctly during upgrade. The fix is not Rebuild Data — it is recreating the memorised report group. All other QB functions and your company file data remain unaffected.

The compatibility mode catch: You must disable compatibility mode in two places — the QB desktop shortcut AND the QBW32.EXE file in the QB installation folder. Doing only the shortcut will not fully resolve C=272 caused by compatibility mode. Most guides only show the shortcut step.

What Causes QuickBooks Error C=272?

Company File Data Corruption

Primary cause when C=272 clears on sample file — minor data corruption in the .QBW file causes QB's Verify or Rebuild utility to encounter a database record with a "target bit set outside the expected range." Rebuild Data repairs most minor corruption automatically. Severe corruption requires restoring from a recent backup.

Windows Compatibility Mode Enabled

Primary cause when C=272 persists on sample file — QB is running under compatibility mode for an older Windows version. QB's database engine makes API calls that compatibility mode intercepts and changes, producing internal conflicts that surface as C=272. Must be disabled on both the QB shortcut and the QBW32.EXE file.

Corrupted Memorised Report From Older QB Version

A memorised report created in an earlier QB version was not fully converted during a QB upgrade. The unconverted data structure is unreadable by the current database engine — producing C=272 specifically when that report is opened. All other QB operations remain unaffected. The fix is recreating the report group, not touching the company file.

Printing 1099 or W2 Forms

A documented C=272 trigger in specific QB releases: attempting to print 1099 or W2 forms produces the error (sometimes shown with code V6.OD R1 [M=1477, L5203, C=43]). This is a version-specific compatibility issue — updating QB to the latest release typically includes a fix for this particular C=272 trigger.

Damaged or Incomplete QB Installation

A partial or corrupted QB installation leaves database engine components in an inconsistent state — causing C=272 during data utility operations even when the company file itself is healthy. The Install Diagnostic Tool or a clean reinstall replaces the damaged components.

Virus or Malware Damage

Malware that corrupts QB program files or the company file can produce C=272 during data validation. Run a full antivirus scan before attempting QB repairs — reinstalling QB will not help if malware is actively damaging program files during the repair process.

How to Fix QuickBooks Error C=272

Run the sample company file test first — 60 seconds, tells you exactly which path to take.

METHOD 1 Run Verify Data + Rebuild Data C=272 clears on sample file — company file corruption
1

QB Desktop → File → Utilities → Verify Data. Wait for completion. If it reports "QuickBooks detected no problems with your data" — the error may have been transient. Retry the original action. If it reports issues — proceed to Rebuild.

2

File → Utilities → Rebuild Data → OK. QB will prompt you to create a backup — do so. Let Rebuild run to completion — it may take several minutes on large company files. After it finishes, click OK. Run Verify Data again to confirm no remaining issues. Retry the action that produced C=272. If Verify still reports damage after Rebuild — the corruption is severe and requires restoring from a pre-corruption backup, then re-entering any transactions since the backup date.

METHOD 2 Disable Windows Compatibility Mode — Both Locations C=272 persists on sample file — compatibility mode

Must be done in two places. Disabling compatibility mode only on the QB shortcut but not on QBW32.EXE — or vice versa — will not resolve C=272. Both must be cleared.

1

QB Desktop shortcut: Right-click the QuickBooks icon on your desktop → Properties → Compatibility tab. If the box "Run this program in compatibility mode for" is checked — uncheck it → click OK. If it is already unchecked → click Cancel and move to step 2.

2

QBW32.EXE file: Right-click the QB icon → Properties → Shortcut tab → click Open File Location. In the QB installation folder, locate QBW32.EXE. Right-click it → Properties → Compatibility tab. Uncheck "Run this program in compatibility mode for" → click OK. Close all properties windows. Restart QB and retry the action that produced C=272.

METHOD 3 Recreate the Memorised Report Group C=272 only when opening a specific memorised report
1

Reports → Memorised Reports → Memorised Report List. Click Memorised Report dropdown → New Group → name it "Z Do Not Use" → OK.

2

Right-click each non-working memorised report → Edit Memorised Report → check "Save in Memorised Report Group" → select Z Do Not Use → OK. Repeat for every report that produces C=272.

3

Click Memorised Report → Re-sort List → OK. Close QB and reopen. Now recreate the affected reports from scratch — run the report in QB normally, then memorise it: Reports → Memorise Report → name it → Save. The fresh version is built in the current QB version's data structure and will not produce C=272.

METHOD 4 Install Diagnostic Tool + Repair + Clean Install All above tried — damaged QB installation
1

Install Diagnostic Tool: Tool Hub → Installation Issues → QuickBooks Install Diagnostic Tool → run → restart (20 min). This repairs corrupted .NET Framework, MSXML, and C++ Redistributable components that QB's database engine depends on. Repair QB: Control Panel → Programs and Features → QuickBooks → Uninstall/Change → Repair → follow prompts → restart → update QB afterwards. Clean Install (last resort — backup first): Tool Hub → Installation Issues → Clean Install Tool → accept → select version → Continue. After removal, reinstall from your installer. A clean install replaces every program file including all database engine components.

Quick Reference

Your situation Likely cause Start with
C=272 clears when opening sample company file Company file data corruption Method 1 — Verify + Rebuild Data
C=272 persists even on sample company file Windows compatibility mode or QB install Method 2 — disable compatibility mode (both)
C=272 only when opening one specific report Corrupted memorised report from old QB version Method 3 — recreate report group
C=272 when printing 1099 or W2 forms Version-specific bug Update QB to latest release first

Frequently Asked Questions

Will running Rebuild Data cause data loss?
Rebuild Data does not intentionally delete transactions or financial data — it repairs the internal data structure of the company file. However, QB requires you to create a backup before Rebuild starts, and you should take that seriously. In rare cases where the corruption is too severe for Rebuild to fix, QB reports the unfixable records and you would need to restore from a pre-corruption backup. This is the only scenario where you would need to re-enter transactions made since the backup. For this reason, frequent backups are essential — they limit the re-entry exposure if a severe corruption ever occurs.
Why does disabling compatibility mode need to be done in two places?
Windows stores compatibility settings separately for each executable file — meaning a shortcut and the executable it points to can have different settings. The QB desktop shortcut is a separate object from QBW32.EXE. If you disable compatibility mode on the shortcut but not on QBW32.EXE (or vice versa), one of them still runs QB under the incorrect compatibility layer and C=272 continues. The shortcut controls how QB is launched from the desktop; QBW32.EXE controls the process-level compatibility settings. Both need to have "Run this program in compatibility mode" unchecked for the fix to be complete.
Why does recreating the memorised report group fix C=272 for reports?
Memorised reports are stored inside the company file as serialised report definitions — a snapshot of all settings (date ranges, columns, filters, sort order) at the time the report was memorised. When a company file is upgraded from an older QB version, some of these serialised definitions do not fully convert to the new format. The report definition contains data in a structure the current database engine does not recognise — when QB tries to load and render it, C=272 results. Moving the broken report to a "Z Do Not Use" group and re-sorting the list effectively quarantines the corrupted definition without deleting its historical data. Recreating the report fresh in the current QB version writes a new serialised definition in the correct format — and this version opens and runs without error.

Related QuickBooks Errors

Error C=272 Persisting After Rebuild and Compatibility Fix?

Let QuickFix Bookkeeping Fix Your Company File Data.

Certified Intuit ProAdvisors — Data Repair Specialists

Persistent C=272 after Rebuild Data, compatibility mode fix, and memorised report recreation typically means deeper file corruption requiring specialist-level data repair tools beyond the standard QB utilities.

Book a Free 30-Minute Consultation

No obligation. Same-day response. Data integrity restored fast.