[QODBC Online] Querying Multiple QuickBooks Online Company Files Simultaneously via Power BI with QODBC Online

Problem Description:

When using QODBC Online to consolidate data from multiple QuickBooks Online (QBO) company files simultaneously through Power BI, queries may fail with Error 653 ("There was an error while communicating with the Ids Server - The Response Stream was null or empty") and/or port 8383 binding issues. Consolidated P&L queries across 6+ company files fail, while pulling one file at a time succeeds.

Affected products: QODBC Online, QuickBooks Online, Power BI
Expected outcome: By limiting consolidated queries to 2–3 company files at a time and managing connection cycling, errors can be avoided. QODBC Online itself does not limit simultaneous connections - the limit comes from Intuit's API side.

Symptoms:

• A consolidated Power BI query that pulls P&L data from multiple QBO company files works when pulling one file at a time, but fails when consolidating 4+ files simultaneously.
• Error message: "OLE DB or ODBC error: [DataSource.Error] ODBC: ERROR [00000] [QODBC ONLINE] QuickBooks message: 653 - There was an error while communicating with the Ids Server. - The Response Stream was null or empty."
• Port 8383 becomes unavailable without any configuration change from the user.
• The issue is specific to QuickBooks Online (not QuickBooks Desktop) and occurs when multiple company files are queried concurrently.

Cause:

While QODBC Online does not impose any limit on the number of simultaneous company file connections, Intuit's API does have rate limits and concurrent connection limits. When Power BI queries multiple QBO files simultaneously (especially through a consolidated query), the Intuit API may reject requests due to:

1. Concurrent API connection limits: Intuit restricts how many simultaneous API connections a single application/user can maintain.
2. Response stream timeout: When too many files are queried at once, the response stream may time out or return empty, resulting in Error 653.
3. Port 8383 overload: The QODBC Online communication port can become overloaded by simultaneous large data extracts from Power BI.

Environment:

Solution:

1. Limit consolidated queries to 2–3 company files at a time. This is the recommended workaround to avoid Intuit API rate-limit and timeout issues. Instead of pulling data from all 7 companies in one query, split into batches of 2–3 files per refresh cycle.
2. Cycle through incremental consolidations. Pull P&L for 2–3 files, refresh Power BI, then pull the next 2–3 files, and so on. While more time-consuming, this is the most reliable approach.
3. If port 8383 becomes unavailable: Try restarting your machine to clear any stale port bindings, then test again.
4. Avoid querying too many files simultaneously. While QODBC Online does not limit connections, Intuit's API does. Keep concurrent queries well below the number of available company files.

SQL Examples:

Example - Splitting a 7-file consolidation into batches of 3:

-- Batch 1: Companies A, B, C
SELECT * FROM ProfitAndLoss WHERE Company IN ('A', 'B', 'C')

-- Refresh Power BI after batch 1 completes

-- Batch 2: Companies D, E, F
SELECT * FROM ProfitAndLoss WHERE Company IN ('D', 'E', 'F')

-- Refresh Power BI after batch 2 completes

-- Batch 3: Company G (remaining)
SELECT * FROM ProfitAndLoss WHERE Company = 'G'

Example Scenarios:

Scenario 1 - Consolidating P&L from 7 QBO companies:

A company uses Power BI to consolidate P&L data from 7 QuickBooks Online company files. A single consolidated query across all 7 files fails with Error 653 and port 8383 issues. The fix was to split the consolidation into incremental batches of 2–3 companies per refresh cycle. Each batch completes successfully before moving to the next.

Scenario 2 - Power BI data refresh timeout:

A scheduled Power BI data refresh across 6 QBO files fails intermittently with "Response Stream was null or empty." The issue is Intuit API rate limiting when too many concurrent requests are sent. Limiting the refresh to 2–3 files per cycle eliminates the error.

Additional Notes:

• This limit comes from Intuit, not QODBC. QODBC Online acts as a pass-through to the Intuit API - it does not impose its own connection limits. The rate-limiting behavior is controlled by Intuit's infrastructure.
• Error 653 specifically means the response from the Intuit IDs Server was empty or timed out. It is NOT a QODBC bug - it is an API-level timeout caused by overloading the connection pool.
• Port 8383 is used by QODBC Online for communication with the IntIds server. If it becomes unavailable after a Power BI query completes, restarting the machine typically resolves the binding issue.

Related Articles:

Using QuickBooks Online Data with MS SQL Server via QODBC Online Troubleshooting: Slow Performance/Cannot Get Full Records From QuickBooks

Keywords: