How to create Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC POS/QRemote

Start your "SQL Server Management Studio"

Login to your SQL Server.

On the Left-hand side panel, you will find the Server, Right Click on the "SQL Server" and Select Properties.

Please Verify that your SQL Server is 64-bit.

64 and 32-bit worlds are kept totally separate in the Microsoft Windows Operating System. QuickBooks is a 32-bit application, so in order to communicate with it, a 32-bit ODBC driver is required.

QRemote works as a bridge between 64-bit Applications and the 32-bit QODBC Driver by communicating data calls between the two worlds using TCP/IP protocol.  QRemote makes it possible for 64-bit Web Servers and 64-bit applications to talk to QuickBooks live for the first time via the QODBC Driver.

Since a 64-bit application cannot talk to a 32-bit driver, we have to do a bit of magic to get the worlds to connect, we call it QRemote.

QRemote also works for 32-bit application as an alternative to Dcom.  As SQL Server is a service based application it has to either use Dcom or QRemote.

QRemote has two components “QRemote Client Driver for QODBC” and “QRemote Server for QODBC” 

QRemote Client Driver: Allows 64-bit Applications to connect to QRemote Server and sends the Request to QRemote Server for Processing.  

QRemote Server : Processes requested instruction from QRemote Client to QuickBooks using QODBC DSN Driver. 

Start “QRemote Server for QODBC POS” from the start menu. ( If QRemoteServer is not running ) 

Double click the QRemote Server icon from the system tray

QRemote Server Main screen shows the IP address and Port it allows the QRemote Client to connect to.

Make a note of IP address and Port number listed on the QRemote Server “Event Logs window”

Create a new DSN entry/or configure the existing one

Navigate to Start Menu, QODBC Drivers for Use with QuickBooks POS and click

Configure QODBC POS Data Source 64-bit

"QuickBooks POS Data 64-bit" is the default DSN created when installing QODBC.

For 32-bit SQL Server change, QRemote DSN to "QuickBooks POS Data QRemote" is the default DSN created when installing QODBC.

Configure the DSN and provide the IP address and Port as listed under “QRemote Server”

Under the QRemote for QuickBooks – Client  DSN configuration screen, Please fill in the following information 

• Data Source Name: Name of your DSN entry 
• Server: IP address displayed on QRemote Server 
• Port: Port displayed on QRemote Server 
• Encryption Key :   

    (Keep Encryption Key empty/blank. In case you want to use encrypted data transfer between QRemote client and QRemoteServer, You can configure your encryption key on QRemoteServer and use the same on QRemote Client DSN) 

• Remote DSN: select the QODBC POS DSN from the list. ( Make sure QRemote Server is running) 

Start Your QuickBooks POS.

Run MS SQL 2005 Dev / 2008 / 2012 (64-bit) and Login in

    Run SQL Server Management Studio, you'd better choose the SQL Server Authentication and then input right name password. 

Under SQL Server Management Studio , Navigate to “Server Objects” -> Linked Server  -> New Linked Server

 OR

Provide the “New Linked Server” information

On Clicking OK, it will start establishing connection to QuickBooks,  Please accept the certificate for allowing data access on QuickBooks

After you have accepted the Certificate, the Linked server will be shown under “Linked Server” Category.

Configure MSDASQL (Microsoft OLE DB Provider for ODBC Drivers)

   The OLE DB provider options for managing linked queries can be set in SQL Server Management Studio. In Object Explorer, right-click the provider name and select Properties for MSDASQL.

Dynamic parameter should be checked to allow parameter queries. Level zero only should be checked to allow four-part naming to work. Allow InProcess should be checked to help performance. Non transacted updates should be checked if you want to be able to update QuickBooks data. Index as access path should be checked to help performance. Disallow adhoc accesses should be unchecked to allow OPENQUERY to function.

QODBC/QRemote is ready to use with SQL Server/Linked Server

Execute below query

Select * from qremote…customer

On each query, QRemote Server Logs the events, If you are facing any issues or delay in response, please refer QRemote Server Event Logs for details on which stage it's taking more time.

Another Test

Select * from qremote…employee

On each query, QRemote Server Logs the events, If you are facing any issues or delay in response, please refer QRemote Server Event Logs for details on which stage its taking more time.

Errors and Solutions 

“[QODBC-POS] QODBC-POS  Server Edition License Required.”

The QODBC CDKEY License you have activated is not of Server edition.  Please contact our Sales or Support team . http://support.flexquarters.com/esupport/

“[QODBC-POS] Evaluation Expired”

You have run out of the 30-day trial/evaluation version, If you still wish to evaluate QODBC, Please contact our Sales team.

“QRemote” or “QODBC” contains multiple tables that match the table “TableName”

This means you have not configured “MSDASQL” provider. Please refer above steps and configure “MSDASQL” provider

“[QODBC-POS] Unable to Open License File”

Please download QDemo application by clicking here.

Please run QDemo application as Administrator.

Please change connection string DSN=QuickBooks POS Data 64-bit; OLE DB Services=-2;

Please click on "Test Connection". It will start establishing connection to QuickBooks, Please accept the certificate for allowing data access on QuickBooks

Now please click on "Run Query". It should display table list.

Now please test connection on the linked server by right click on linked server name, Please click on "Test Connection".

You will receive Test Connection success message.

Please Refer :

Using QuickBooks data with MS SQL Server using QODBC Driver and QRemote (Video)

QODBC Reports Architecture Mismatch Problem When connecting

Accessing QuickBooks Data Remotely using QODBC & QRemote. (Video)

Keywords: SQL Server 2008 Management Studio, SQL Server 2016 Management Studio, SQL Server 2012 Management Studio, SQL Server Management Studio, SSMS