Skip to main content
Solved

Issue with CData QuickBooks ODBC Driver after Purchase

  • August 11, 2025
  • 1 reply
  • 54 views

Forum|alt.badge.img

Hello everyone,
I recently purchased the CData QuickBooks ODBC Driver (Desktop version, $499/year) for one desktop and one data source (QuickBooks), as shown in the attached image.

When trying to use it in Navicat Premium to query data, I get the following error:

 

1003 - The feature is only available with an Enterprise server license of CData Provider for QuickBooks 2024.

I’m attaching screenshots of both the purchase and the error.

My questions are:

  • Why is it asking for an Enterprise Server License if I bought the Desktop version?

  • Is there any configuration I need to change for it to work in my current setup?

My final goal, after successfully testing with Navicat, is to connect to QuickBooks from a Laravel application.

Thanks in advance for any guidance.

Best answer by Brooks E

We are sorry that you are facing this issue! 

There are a few reasons that this manner of error could occur. 

The most common reason would be the use of SQL Gateway with the ODBC Driver, which requires a Server-level license regardless of where the ODBC Driver and SQL Gateway tool are installed. 

Another common reason is use of the driver on a VM, which can confuse the licensing check. 

In any case, the nuance behind such an issue typically requires further investigation. We recommend reaching out to [email protected] with details of such an issue, and from there our qualified Support Team can further assist you to help get things running as needed. 

This topic has been closed for replies.

1 reply

Forum|alt.badge.img
  • Employee
  • Answer
  • August 12, 2025

We are sorry that you are facing this issue! 

There are a few reasons that this manner of error could occur. 

The most common reason would be the use of SQL Gateway with the ODBC Driver, which requires a Server-level license regardless of where the ODBC Driver and SQL Gateway tool are installed. 

Another common reason is use of the driver on a VM, which can confuse the licensing check. 

In any case, the nuance behind such an issue typically requires further investigation. We recommend reaching out to [email protected] with details of such an issue, and from there our qualified Support Team can further assist you to help get things running as needed.