Using the Windows Explorer Security tab, you also need to give read and write rights to the QuickBooks application folder (normally C:\Program Files\QODBC Driver for QuickBooks\) to the group that contains the appropriate web users too. This allows for the creation and update of QODBC trace and message logs and allows access to the DCOM server executables.

It seems you still have a security setup issue. Please switch off the QODBC optimizer and download the following simple example by clicking here: qbcust.zip. Open the zip file and extract qbcust.asp. Save the file on your Local Disk in the \Inetpub\wwwroot folder as shown here:

Launch your browser (making sure QuickBooks is currently running on your computer with your company file open) and run the example by entering the following URL in your browser :-

http://localhost/qbcust.asp

The following should be displayed on your browser (with your data) and let me know how the Admin and other Web Users work? :-

QODBC Customer Web List Demo Page
Preparing to Create Connection Object
ADO Connection Created
ADO Recordset Created - Opening QuickBooks Sample Company File

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[QODBC] QB Begin Session Failed. Error = 80040416, If QuickBooks is not running, a call to the "BeginSession" method must include the name of the QuickBooks company data file.

/qbcust.asp, line 30

The error is saying that QuickBooks isn't running. Try starting QuickBooks and opening the company file on the server console (local session) first.

It that works, see: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running?

QODBC Customer Web List Demo Page
Preparing to Create Connection Object
ADO Connection Created
ADO Recordset Created - Opening QuickBooks Sample Company File

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[QODBC] QB Begin Session Failed. Error = 80040416, If QuickBooks is not running, a call to the "BeginSession" method must include the name of the QuickBooks company data file.

/qbcust.asp, line 30

The above message is saying that the QuickBooks Data DSN used by the qbcust.asp test file doesn't specify what company file to use. You need to add the company file path to the QuickBooks Data DSN as per: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running?

I also thought you said that when logged in as the Administrator it works?

If that's the case, you are going to need to go back and setup Anonymous access in IIS. Trying to resolve why your Terminal Server logins don't work through a web application is a Windows Terminal Server security issue.

Reading your first post, I believe if you give the Terminal User administrator rights your web application will work also.

It does work when you login to the web app as Administrator - in fact - the other user I'm trying (the one that doesn't work and gives me the 80070005) is a member of the Domain Admins group - so therefore is locally on the SBS server a member of the Administrator's group. 

When you sent your test file you didn't mention any authentication - which confused me a bit - but I thought oh well - go ahead and go for it - so I put it out at the webserver root - which does not force authentication.  Upon your last reply I moved your file into the same directory as my application - so it is under exactly the same auth rules.  QB is loaded on the server console with a data file open.  I still get this error message when I try to access your test file - even when logged in as Administrator:

QODBC Customer Web List Demo Page
Preparing to Create Connection Object
ADO Connection Created
ADO Recordset Created - Opening QuickBooks Sample Company File

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[QODBC] QB Begin Session Failed. Error = 80040416, If QuickBooks is not running, a call to the "BeginSession" method must include the name of the QuickBooks company data file.

/felix/qbcust.asp, line 30

As before, the error message is still saying that the QuickBooks Data DSN used by the qbcust.asp test file doesn't specify what company file to use. You need to add the company file path to the QuickBooks Data DSN as per: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running?

QODBC Customer Web List Demo Page
Preparing to Create Connection Object
ADO Connection Created
ADO Recordset Created - Opening QuickBooks Sample Company File

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[QODBC] QB Begin Session Failed. Error = 80040406, Could not determine the version of the QuickBooks company data file, or the data file has been modified and requires a newer version of QuickBooks.

/felix/qbcust.asp, line 30

QuickBooks needs to be closed when you run:

http://localhost/qbcust.asp

Did you check that "auto-login" unattended mode works correctly? Using VB Demo you should be able to use the "QuickBooks Data" DSN without running QuickBooks.

Well - this is QB Premier 2004 so the auto-login configuration boxes are checked off in the ODBC config.  When I run VB Demo against the same DSN that I'm testing with qbcust.asp it works fine - running the demo from terminal services with QB still running - same company file open - on the console.  I'll have to physically get to the console to close QB to do the test you mentioned - I was under the impression that QB should still be open with the company file open as per your 5-13 post since the result of that was failure. 

This is also SBS SP1 if that makes a difference...I know some security model stuff got changed for IIS and ASP

The Advanced tab in QODBC Setup v6 Build 148 and later now has new defaults for Integrated Application Defaults Authorization popup settings. These settings are only available to USA QuickBooks 2005 and USA QuickBooks 2006 users, otherwise they are greyed out. But, that doesn't mean that you don't need to setup auto-login unattended mode as instructed, because you still do.

In order to get a IIS/QODBC/QuickBooks connection going, auto-login must work. Using VB Demo you should be able to use the "QuickBooks Data" DSN without running QuickBooks. You cannot run a IIS connection and have QuickBooks running on any Terminal Server users either. See: W2K3 Terminal Server / QB2006 Ent. + QODBC  for more information.

Tom,

How does this apply to me?  I'm running QB 2004 - not '05 or '06 and the only reason I was using terminal services at all was to test the VB Demo software - which worked just fine. 

It seems to me that we've gotten way off track from the original problem and are now troubleshooting our troubleshooting steps instead of troubleshooting the problem.  Let me restate the original problem if I can - perhaps we can refocus on that:

SBS 2003 SP1 with IIS

QB Premier 2004

QOBDC server edition (version 5 with version 6 installed over the top) in DCOM mode

Web application running inside IIS (php application) referencing the QODBC System DSN pointing to a specific QB file in "Same as company file" mode - optimizer turned off - remote connector turned off - online edition turned off - DCOM enabled. 

The web application works wonderfully when logged into the web application as Administrator.  I get 80070005 errors when logging into the web application as any other user (even if they are a member of the Domain Admins group).

Perhaps I'm not understand what you are trying to communicate to me with the cut and paste of your documentation.  Am I missing something?

Thanks...

JD

I have also reviewed this on one of my systems that was working with QODBC v5, and basically it stopped working as soon as I installed QODBC v6. I had to reconfigure the directory permissions and DCOMs again from scratch and reboot to get QODBC v6 going again. So regardless whether your web pages worked using QODBC v5, when you upgrade to QODBC v6 you must go through the whole DCOM setup procedure again just like it's brand new.

Installing Terminal Server does change how QODBC works and that's why I referred you to: W2K3 Terminal Server / QB2006 Ent. + QODBC as QODBC needs to work with QuickBooks running on the server's local session, not a Terminal Server session.

Tom,

Any progress on this issue??

Thanks.

JD

I have often had to use the QODBCSetDCOM.VBS VB script to correct the setup to the DCOM Servers regardless whether they appear correctly setup or not. QODBCSetDCOM.VBS will reset and automatically add all necessary security each time it is run. The script can be edited if you need to change the Accounts it is configuring.