I’m having a problem getting the 2007 qodbc upgrade to work on our Windows 2003 server.

Some history:  We have been using the 2005 web server version of QODBC successfully, on a Windows 2003 Server (SP1), with QuickBooks Enterprise Edition, for a year and a half.  We did not do the 2006 upgrade.

After some amount of difficulty, I was able to get the QODBC 2007 upgrade to work in my XP development machine (I had to follow the 17 step procedure outlined in “After upgrading to QuickBooks 2006, QODBC auto-login unattended mode no longer works?”, etc).  When upgrading the server to QuickBooks 2007 and QODBC 7.00.00.204, I did it a little differently.  I first eliminated FlexQuarters QODBC from the list of integrated applications before converting the QBW file from 2005 to 2007 (to avoid the 17 step procedure), installed the QuickBooks upgrade then the QODBC upgrade.

The first problem is that the sample file sample05.qbw file was not upgraded (to QuickBooks 2007 format), so the QODBC Test VBScript test didn’t work.  It took me a while to figure that out, but when I upgraded the sample file, the QODBC Test VBScript test worked.

I performed all of the procedures described in

http://www.qodbc.com/QODBCweb.htm, including the Trouble Shooting section, except for reinstalling Windows 2003 Server, which is not an acceptable solution.

“After upgrading to QuickBooks 2006, QODBC auto-login unattended mode no longer works?”

How can I see QuickBooks data in a Internet Explorer Browser using Windows XP? except for “Uncheck the "Allow IIS to control password" setting for Anonymous access in IIS as shown here and set your own password” because that is not available under Windows 2003 Server.

With the following results:

The DCOM test page works.

The VB Demo application works, even in auto-login mode.

The DisplaySQL application does not work in any mode.  Neither does the qbcust application.  I think they are both hanging on the initial connection to QuickBooks.

The problem is that I don’t know what to try next, as there is no indication anywhere as to what might be wrong.  The trace log file, QODBCTRA.TXT is empty (yes, I selected Detailed Tracing).  QODBCLOG.TXT is empty as well, and nothing shows up in qbsdklog.txt, nor any of the Windows 2003 event logs.  When running these applications, the server beeps once, as if to say there is something wrong, but I cannot find any indication as to what is wrong.

I’m wondering if part of the problem might be location confusion on the part of QODBC.  My initial 2005 installation of QODBC was in the E:\Program Files directory (as I typically do not install programs on the C: drive), and I put the upgrade there as well, and while everything worked fine with the 2005 version, might QODBC be confused about the locations of the various log files?  Especially since there is another version of QODBC loaded on the machine (the read-only one that now comes with QuickBooks 2007).  Do you think it would be fruitful to uninstall and reinstall QODBC on the C drive?  If I do that, do I need to deactivate and reactivate it?

Other than that idea, which seems like a stretch, I really don’t know what to try next, as, as far as I can tell, I’ve done everything listed on your website, and I have no information about why the test applications are still failing.  Any clue that might at least give me a detailed error message?  What to try next?

When using Windows 2003 Server you also need to check your "Enhanced Security Configuration for Internet Explorer" settings.

The Enhanced Security Configuration for Internet Explorer typically sets the IE security settings to "high", so QuickBooks throws a warning every time it starts, even for the SYSTEM service, which hangs QODBC while waiting for input.

Check your DCOM settings as per: How do I manually setup the QODBC DCOM Servers on Windows XP Pro and Windows 2003 Server? and check your security settings for the QODBC program folder (whereever that be...).

Tried your suggestions with no change.  Checked the DCOM settings -- they were already okay.  The security settings on the QODBC program folders (the one that I installed in, and the one that comes with QuickBooks 2007) were okay as well.  Set the browser (IE 6) security settings to low.  Even tried setting the Authentication Level to None on the qbXMLRPxxx components.  No change in the results -- DCOM Test page works, VB Demo works.  DisplaySQL hangs.  Nothing in any of the qodbc or qbsdk logs, nor the windows event viewer, but the server still beeps when I try to run DisplaySQL.

Don't know if this is significant -- the TestDCOM program only displays QB2002 - 2005, DCOM and COM.  Nothing about QB2007.  Also, when I run VBDemo, the trace file lists the highest QB Supported Version as 6.0.

Keep in mind that this all worked just fine for a long time when I was on QODBC 5 (and QuickBooks 5).  What changed between those version that would cause the behavior I'm seeing?  What to try next?

Ran QODBCSetDCOM.VBS again and rebooted with no luck.  Before I ran it again, I did verify that it was finding the qbXMLRPE... files on the coreect drive.  I also added the user IWAM_servername, becuase its also an IIS related user.  When you say "change Accounts", do you mean Users (as I did with IWAM_servername) or something different.?

When QODBCSetDCOM.VBS runs the result is a screen that, for both qbXMLRPE files, lists the set of users in the script as "Launch Allowed" and "Access Allowed", and no users under "Luanch Denied" and "Access Denied".  I assume this is the desired result?

Same end result -- DCOM test program and VBDemo work, DisplaySQL hangs with a beep and no messages anywhere.  It makes sense that it's a security setting, but I'm not getting any information to try to track it down.

Any ideas on getting more specific information about the security error? What to try next?

Uninstalling and reinstalling both QuickBooks and QODBC, on the C: drive, worked.  Had to follow the trouble shooting tips up through the setting of permissions for c\windows\system32\fqqbc32.exe, c\windows\system32\fqqb32.dll, etc.

Not sure if it was the reinstall in general, or the fact that it's now on the C: drive, that made the difference.

Thanx.