QuickBooks SDK Error 80040408 ("Could Not Start QuickBooks")? It's a Launch Conflict
A QuickBooks SDK integration (via QBXMLRP2RequestProcessor) fails with 80040408 / 0x80040408: “Could not start QuickBooks.”
Check the session and launch configuration: 80040408 can occur when QuickBooks is already running with a different file, Quick Startup holds an instance open, the file path does not match, or the SDK app and QuickBooks run at different privilege levels. These checks come before attempting data-file repair.
Fix 1: Close every QuickBooks instance
- Close QuickBooks.
- Open Task Manager → Details and end any lingering QBW32.exe / QBW.exe and QBCFMonitorService-spawned QB processes.
- Relaunch and let it settle at the No Company Open window.
Fix 2: Disable “Keep QuickBooks running for Quick Startup”
Quick Startup leaves a hidden QB instance that the SDK collides with:
- Edit → Preferences → General → My Preferences.
- Untick “Keep QuickBooks running for quick startups.”
- Close QuickBooks fully, then try the integration again.
Fix 3: Match privilege levels and the file path
- If your SDK app runs as administrator, run QuickBooks as administrator too (or both normal) — a mismatch causes 80040408.
- Ensure the app is asking for the exact company-file path that’s open (or let it use the currently-open file).
Fix 4: Confirm authorization
In QuickBooks: Edit → Preferences → Integrated Applications — make sure your SDK app is listed and allowed to auto-login while the company file is open.
FAQ
Should QuickBooks be open or closed when the SDK connects? For most SDK apps, leave QuickBooks open at the No Company / your company file as the right user — not mid-dialog and not with a second file open.
Same code via the Web Connector (QBWC1013)? See QBWC1013 — same “could not start” cause, Web-Connector flavor.
Sources: Intuit Developer — Troubleshooting “Could not start QuickBooks”