QODBC Web Server Edition Instructions
It’s important for you to know first off that QODBC is not a system that can talk directly to the QuickBooks data file like other ODBC drivers. QuickBooks accounting rules must be respected in order to keep the financial system in balance, so our driver communicates with the copy of the QuickBooks program running on your machine using the Intuit SDK interface, which is fully supported by Intuit.
Our web version of QODBC will allow you to use any web tool you wish to use (ASP, PHP, Cold Fusion) to access data live from QuickBooks without conversion.
The web version is a separate product from the normal desktop editions of QODBC. The reason for this is twofold:
Firstly, as a licensing issue, we must allow for use by potentially hundreds of logins to the machine remotely using the web.
Secondly, QuickBooks does not run as a system service (background task) which is what IIS Web Server Software runs as, so we have developed special software to allow us to communicate with QuickBooks running on the server console.
You can upgrade to the Web Server Edition from the Read/Write version at any time for the difference in price.All of our products support QuickBooks USA versions 2019-2002, UK or Canadian 2019-2003. QuickBooks Pro, Premiere and Enterprise editions are supported. QuickBooks Online edition is supported.
You have two choices in setting up the Web Server Edition. The first is using the QODBC DCOM Servers. The second is using the Remote Connector Option.
The DCOM Servers require QuickBooks to be running on the Server Console. They are more secure and require no extra overhead but are more rigid on how it is setup and it can be difficult to configure the security of the DCOM servers.
The Remote Connector option allows the window that is running QuickBooks to be anywhere that is accessible via TCP/IP. That means QuickBooks can be run in a Terminal Sessions window, on another computer on your LAN or anywhere on the WEB. If your data will be transmitted over the internet we recommend you upgrading the Remote Connector to the SSL secure version. The instructions on setting up the Remote Connector version are
Basic Setup For Using the DCOM Servers Method
You must turn on use of the DCOM servers. You do this by running the QODBC Setup Screen and pressing the “Advance” button. Check the checkbox for “Use DCOM Servers”.
Ensure the following are installed and registered on your server:
- A supported version of QuickBooks 2004 or 2003 (with company file set to Multi-user Mode)
- QuickBooks must be running on the server console, not a terminal services session.
- Microsoft Internet Information Server (IIS5 or later), Apache or Cold Fusion.
- If running ASP.NET, make sure the .NET framework is loaded and patched to the current release level. Also verify that MDAC 2.6 or greater is installed.
- QODBC Driver for QuickBooks registered as Web Server Edition – you can download the most current build below.
- Give read and write rights to the QuickBooks application folder (normally C:\Program Files\QODBC Driver for QuickBooks\) to the Internet Guest Account (IUSR_<machine_name>), ASP.NET Machine Account (ASPNET) and INTERACTIVE. This allows for creation and update of QODBC trace and message logs and allows access to the DCOM server executables.
- Give the Internet Guest Account (IUSR_<machine_name>), ASP.NET Machine Account (ASPNET) and INTERACTIVE accounts permissions read and write the following file in your System32 directory, I9K4UQLW.ocx. It may be a hidden, system file.
- Configure QODBC DCOM servers. DCOM qbXMLRP2eInteractive.exe is for accessing QB2004, and DCOM qbXMLRPeInteractive.exe is for accessing QB2002 and
- Test your DCOM setup.
- IIS users download: TestDCOM.ASP
- PHP users download: TestDCOM.PHP
- Cold Fusion download: TestDCOM.CFM
- If you are using ColdFusion you need to create an ODBC Socket Data
Source. Click for ColdFusion Data Source Setup Instructions.
- You can use the built-in “QuickBooks Data” System DSN which points to the currently open QuickBooks company file (.). The QuickBooks application can only access one file at a time, so your web application will be limited to the single open company file.
- Download and copy a sample script to your Web Site Scripts Directory.
- IIS users download: DisplaySQL.ASP
- PHP users download: DisplaySQL.PHP
- Cold Fusion download: DisplaySQL.CFM
- Start QuickBooks on the console desktop and open the QuickBooks Company file you wish to use.
- Access the Website using a browser. Point to the script on your server. You should get a customer list.
Running QuickBooks Remotely
To allow a web server to access your QuickBooks data on any machine remotely via local area network or via the Internet, use our Remote Link function. We highly recommend
that you purchase the SSL encrypted version upgrade of the remote link when sending data over the open Internet.
If you get a timeout error, or error 5 when trying to test the connection, follow these steps to narrow down the problem:
Is QuickBooks running with a Company file open on the server console? This is required. It cannot be running in a Terminal Services window.
Verify that the QODBC driver runs correctly on the Server Console by running the VBDemo on the QODBC Driver for QuickBooks start menu.
You may have DLL’s which are not registered. After starting QuickBooks and testing and getting errors, check the file qbsdklog.txt (found by running ‘QODBC Setup Screen’, pressing the ‘Messages’ button and then the ‘Review QB SDK Messages’). The bottom of the file contains the most recent errors. Check for details on any errors and how to resolve them.
If you have .DLL issues you can try running the file called Reboot.bat in the QuickBooks installation directory.
Run the TestDCOM script described above. If it does not run at all, your security rights on your web server are preventing it. Make sure that the Internet Guest Account (<IUSR_<machine_name>), and ASP.NET Machine Account (ASPNET) have full rights to read and run scripts in the folder where your TestDCOM script is located.
The TestDCOM script must show “Success” in the rows that correspond to the version of QuickBooks you are using. If you continue to get “Failed” in the rows you need for your version of QuickBooks, you can:
Reset the DCOM security registry information. This is most easily done by running/re-running the Automatic DCOM Configuration Tool. Be sure to reboot before trying the TestDCOM again.
Make sure you gave read and write rights to the QuickBooks application folder (normally C:\Program Files\QODBC Driver for QuickBooks\) to the Internet Guest Account (IUSR_<machine_name>), ASP.NET Machine Account (ASPNET) and INTERACTIVE. This allows access to the DCOM server executables.
Try changing the Anonymous user to Administrator. For IIS that is in the IIS Administration under Directory Security. If this fixes the problem, there is definitely a problem with security rights and you know it can work, simply keep adding security rights until it works. Do not leave the Anonymous user set to Administrator. That is very dangerous.
Run QODBC Setup Screen and press the About button. Verify you are running the Web Server Edition.
Make sure you setup a System DSN, not a file or user DSN for this configuration.
Test the above TestDCOM script first, this script only verifies that the web server can talk your QODBC script and that the installation and security is proper. If this one
works, test the DisplaySQL script.
Check the security on the scripts by right clicking them and choosing the security tab, allow inherited permissions from parent.
If you get stuck, try rebooting the server or stopping and starting the web site, then load QuickBooks, then test the web page.
Give read and execute rights to the Internet Guest Account (IUSR_<machine_name>), ASP.NET Machine Account (ASPNET) to the following files c\windows\system32\fqqbc32.exe, c\windows\system32\fqqb32.dll,
c\windows\odbc.ini, and c\windows\odbcinst.ini.
Check the Application Event log for any messages if you are having trouble with QODBC on the web, all error messages which would normally create a message box on the desktop are sent to the event log in the Web Server Edition.
Turn on Detail Tracking (Slow) by running the ‘QODBC Setup Screen’ and pressing the Messages button and checking the checkbox for ‘Detail Tracing (Slow)’. Run your
script in the browser and return to ‘QODBC Setup Screen’, press the ‘Messages’ button and then press the ‘Review Trace Log’ button. Look for obvious errors.
If simple programs like VBDemo refuse to run, you may have DLLs.
Several of our customers who had trouble getting the Web Server Edition to run without errors, were able to get it running perfectly well after reinstalling Windows
from scratch on the box. Perhaps there were some corrupt system files that prevented proper operation, but if all else fails, try another machine or new OS load.
So isn’t it time you unleashed the full power of QODBC Web Server Edition?
Like our FREE QODBC Basic Edition, you can also try our OBLIGATION FREE 30 Day QODBC Web Server Edition Evaluation to see and write to QuickBooks Transaction Tables from a Web Server! Here are just some of the exciting features of using QODBC Web Server Edition:-
- Access the Transaction Core of QuickBooks Accounting Data
such as Invoices, Bills, Purchase Orders, Checks, Credit Memos, Estimates, Payments, Sales, Employee Time Tracking. Over 80 tables in all!*
- Generate Powerful QuickBooks Reports in your own applications
such as Details on AR & AP, Aging Reports, Balance Sheet, Collections, Transaction Detail, 1099 Detail, Customer Balance Detail, Estimates, Expenses, General Ledger, Income Detail,
Tax Detail, Inventory Detail, Item Profitability, Inventory Status & Valuation, Job Profitability, Open Invoices, Profit and Loss, Open PO’s Sales by Customer, Sales Tax, Time by Job Trial Balance, Vendor Balance Detail & Summary. Over 75 reports total!*
- Free installation support on our web forum.
- Get Discounts on future upgrades to QODBC and our other exciting products.
- Generate your own income by creating Web applications using the QODBC Web Server Edition!