[QODBC Desktop] Power BI (via On-Premises Data Gateway) and QODBC Licensing Requirements

Problem Description:

When using Microsoft Power BI with the On-Premises Data Gateway to access QuickBooks Desktop data, users may encounter connection errors (such as Error = 80040408, Could not start QuickBooks) if the licensing or driver configuration is incorrect. Specifically, the setup is highly dependent on whether the Power BI Gateway and the QuickBooks application are installed on the same machine or different machines within the network.

Affected products: Power BI Desktop, Power BI Service (via Gateway), QODBC Desktop, QODBC Server, QuickBooks Desktop
Expected outcome: After configuring the correct QODBC licenses and driver compatibility (specifically the 3.8 compatibility mode), Power BI can successfully query QuickBooks data, whether the gateway is local or remote.

Symptoms:

• The Power BI service or Desktop application returns an ODBC error: Error = 80040408, Could not start QuickBooks.
• The connection works perfectly when running Power BI locally on the QuickBooks machine, but fails when refreshing data via the On-Prem-Gateway.
• The error explicitly mentions that QuickBooks could not be started or the session failed on the target machine (e.g., Computer Name: OLEMSQBP01).
• The connection works only when the QuickBooks application is manually opened and logged in on the host machine.

Cause:

The connection requirement depends on the network architecture of your Power BI deployment:

1. Single-Machine Architecture: If the Power BI On-Premises Data Gateway and QuickBooks Desktop are both installed on the same machine, only one QODBC license is required (the QODBC Server edition).
2. Multi-Machine Architecture (Remote Access): If the Power BI Gateway is on a separate server from the QuickBooks machine, you need two licenses:
   • On the Gateway Machine: QRemote License, with QRemote Client and Power BI Gateway.
   • On the QuickBooks Machine: QODBC Server Edition license, with QuickBooks, QODBC, QRemote Server, and the QuickBooks company file.
3. Compatibility Mismatch: Recent versions of the QODBC driver/QRemote client may default to a higher compatibility mode than what Power BI's Power Query engine (via the Gateway) expects. For many legacy/standard queries, the 3.8 compatibility mode is required for stability.

Environment:

Solution:

1. Determine your architecture. Identify if your Power BI Gateway service is running on the same Windows machine as your QuickBooks Desktop application.
2. Deploy required licenses.
   • If Single-Machine: Ensure QODEX/QODBC is properly activated on that single machine.
   • If Multi-Machine: Install the QODBC Server edition on the QuickBooks machine and the QODBC Desktop (QRemote) on the Gateway machine.
3. Configure ODBC Compatibility to 3.8 (Crucial Step). To prevent "Begin Session Failed" or "Could not start QuickBooks" errors, manually set the driver to use the 3.8 compatibility mode on both machines:
   1. Navigate to Control Panel → Administrative Tools → Data Sources (ODBC) (3 32-bit) (or 64-bit, as applicable).
   2. Select your System DSN (e.g., 'QuickBooks Data') and click Configure.
   3. Navigate to the Advanced tab.
   4. Locate the ODBC Compatibility dropdown and select '3.8'.
   5. Click Apply and OK.
4. Ensure QRemote Server is running. If using the multi-machine setup, ensure the QRemote Server service is started and accessible on the QuickBooks machine.
5. Verify the connection. Test the connection using the QODBC Test Tool or by performing a manual refresh in Power BI Desktop.

Example Scenarios:

Scenario 1 — Same Machine (Simple): A user has QuickBooks and the Power BI Gateway on their local workstation. They use QODBC Desktop. The connection is straightforward and works as long as QuickBooks is open or Auto-Login is configured.

Scenario 2 — Enterprise Remote Access (Complex): A company has a dedicated Windows Server running the Power BI On-Premises Data Gateway. Their QuickBooks data lives on a separate, highly-secured Accounting Server. To allow the Gateway to pull data, they installed the QODBC Server edition on the Gateway Server and the QODBC Desktop/QRemote driver on the Accounting Server, both configured to 3.8 compatibility.

Additional Notes:

• Auto-Login: For both architectures, it is highly recommended to configure Auto-Login in the QODBC DSN settings. This prevents "Access Denied" errors caused by the user not being logged into QuickBooks.
• Service Account: If the Power BI Gateway is running under a specific Windows Service Account, ensure that the QODBC driver and QuickBooks-related permissions are accessible to that account.
• QS_Error 80040408: This error is almost always caused by the lack of a running QuickBooks session or a failure in the QRemote/ODBC handshake between the two machines.

Related Articles:

Accessing Multiple QuickBooks Company Files Simultaneously with QODBC and QRemote QODBC License Machine Transfer and Deactivation How to Use QODBC with MS Excel Power Query

Keywords: