通过Dbeaver/Java连接QuickBooks执行查询遇XML解析错误求助

Hey there, let's walk through how to diagnose and fix this XML parser error you're hitting with both DBeaver (6.1.5) and Java when running SELECT * FROM CData.QuickBooks.Accounts against your QuickBooks instance. Here are actionable steps to narrow down the issue:

1. Check Your CData QuickBooks Driver Version #

DBeaver 6.1.5 is a fairly old 2019 release, and if you're using an outdated CData driver, it might not handle the XML structure returned by the latest QuickBooks API (whether Desktop or Online). QuickBooks occasionally updates its API response formats, and older drivers can fail to parse these changes.

• Grab the latest compatible version of the CData QuickBooks driver (match it to your QuickBooks type: Desktop/Online) and replace the one in DBeaver's driver library or your Java project.

2. Verify the Query and Object Names #

Double-check that your table reference is correct. Sometimes CData driver schemas or table names can vary based on configuration:

• In DBeaver, browse the database schema directly (expand the connection tree) to confirm the exact table name—maybe it's just QuickBooks.Accounts without the CData prefix?
• Avoid assuming the schema structure; use the driver's built-in metadata to confirm valid tables and columns.

3. Validate QuickBooks Access Permissions #

If your connected QuickBooks user account lacks proper permissions to read the Accounts object, the API might return an unexpected XML response (like an error wrapped in XML) that the driver can't parse correctly.

• For QuickBooks Online: Log into your QuickBooks admin account, go to Users > select the connected user, and ensure they have permission to view/access account data.
• For QuickBooks Desktop: Confirm the user account associated with the connection has the necessary read permissions for the Accounts list.

4. Enable Detailed Driver Logging #

To get to the root of the XML parsing issue, enable verbose logging for the CData driver—this will show you the raw XML response from QuickBooks that's causing the error.

• In DBeaver: Edit your connection, go to the Driver Properties tab, add these properties:
  • LogLevel=VERBOSE
  • LogPath=/path/to/your/logs (use a valid local path)
• In Java: Add these properties to your JDBC connection string:

  String url = "jdbc:quickbooks:LogLevel=VERBOSE;LogPath=/path/to/logs;...your other connection params...";
  

After running the query again, check the log file to see if the XML response is malformed, missing required elements, or contains an API error message.

5. Test a Simplified Query #

Instead of using SELECT *, try a stripped-down query to rule out issues with specific columns:

SELECT Id, Name FROM CData.QuickBooks.Accounts

If this works, the problem is likely with a specific column's XML data (e.g., a special character, null value, or unsupported data type that the driver can't parse). You can add columns one by one to identify the problematic field.

6. Confirm QuickBooks Instance Health #

• QuickBooks Desktop: Make sure the QuickBooks application is running, not in a hung state, and that no other applications are locking the company file.
• QuickBooks Online: Check QuickBooks' status page to ensure there's no ongoing maintenance or API outage that might be returning invalid XML.

内容的提问来源于stack exchange，提问作者user3514641