We have been using QB 2003 and the Server version of QODBC for several years without any trouble.  We upgraded to QB2006 and purchased a new QODBC connector for 2006.  Installation went fine and using the Test Connection everything worked perfecly.  However access now through the web fails.  When using the test DCOM page now the DCOM has permission denied.  I've confirmed the permissions using DCOMCNFG and everything is correct and has not changed.  Any suggestions.

•	•			•		QBXMLRPEQODBCInteractive.exe	Error: Permission denied
•	•				•	QBXMLRP.dll	Success
		•	•	•		QBXMLRP2EQODBCInteractive.exe	Error: Permission denied
		•	•		•	QBXMLRP2.dll	Success
•	•	•	•		•	XERCES-COM.dll	Success

Using the Windows Explorer Security tab, give read and write rights to the QuickBooks application folder (normally C:\Program Files\QODBC Driver for QuickBooks\) to the Anonymous web user IUSR_machinename, ASPNET user and INTERACTIVE. This allows for creation and update of QODBC trace and message logs and allows access to the DCOM server executables.

You also need to create a auto-login company file, see: How do I setup QODBC to auto-login into QuickBooks and start it if it's not running? 

While you have said a lot about QODBC v3 and v6, you haven't indicated what version of QuickBooks is now in use? You will need to have QuickBooks 2005 or 2006 and check that auto-login still works for the company file using VB Demo when QuickBooks isn't running already.

See also: How can I see QuickBooks data in a Internet Explorer Browser using Windows XP? 

Thanks, but you didn't confirm that auto-login still works for the company file using VB Demo when QuickBooks ins't running already? This fails for most 2005 company files that have an existing QODBC Integrated Application Connection when they are converted to the new 2006 format by QuickBooks, see: After upgrading to QuickBooks 2006, QODBC "auto-login" unattended mode no longer works? 

If you are using Windows 2000 Server, you also need to check that IWAM_machinename has access to C:\Program Files\QODBC Driver for QuickBooks\ folder and your Anonymous access settings in IIS.

Otherwise for Windows 2003 Server see: How do I manually setup the QODBC DCOM Servers on Windows XP Pro and Windows 2003 Server? 

qbXMLRPeQODBCInteractive.exe and qbXMLRP2eQODBCInteractive.exe are still the same. Have you restarted the server? Did you understand that the permissions need to be set for the C:\Program Files\QODBC Driver for QuickBooks\ folder too?

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.

I have reviewed this again 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.

Note: It's not possible to run both QuickBooks 2003 and 2006 at the same time and still use QODBC.