QuickBooks Online: Could not start QuickBooks
Overview
The "Could not start QuickBooks" error may occur when using QuickBooks Online via Skyvia Agent if QuickBooks and the Skyvia Agent are running with different user permission levels.
Resolution
Ensure that both QuickBooks and Skyvia Agent are launched with the same permission level — either both as a regular user or both as an administrator. Mixing permission levels (e.g., QuickBooks as administrator and Agent as regular user, or vice versa) can cause this error.
Still Having Issues?
If this does not resolve the issue, refer to the Intuit troubleshooting guide: Troubleshooting: Could not start QuickBooks.
Related Articles
QuickBooks Desktop: Modal Dialog Box Error
Overview When attempting to connect a QuickBooks Desktop company file to Skyvia using Skyvia Agent, you may encounter the following error: Connection to the company could not be established. A modal dialog box is showing in the QuickBooks user ...
QuickBooks Online: The name supplied already exists error
Overview The error "The name supplied already exists. Another customer, vendor, or employee is already using this name" is a limitation returned directly from QuickBooks. It occurs when the Display Name you are trying to create already exists in ...
Running Skyvia Agent in Multiple Workspaces
Overview If you need to use the Skyvia Agent across multiple workspaces, you do not need to reinstall it. A single installed Agent instance can be connected to any workspace by reusing its agent key. Follow the steps below to configure this. ...
Replication: Schema Validation Failed (Absent Columns / Redundant Columns)
Overview If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...
Replication creates extra tables in the database
Overview In some cases, as a result of Replication, in addition to the main tables (for example, dbo.Account), empty additional tables are created in the database with names like: dbo.Account_2ade4447_5e11_4308_9e81_5eab62d9ed52 ...