First of all, whenever using QuickBooks on a network, the same QuickBooks update patch must be applied to every copy of QuickBooks on the network. Once that's correct, have your administrator log into QuickBooks, open the company file, backup the company file, and then: 

1. Edit/Preferences/Integrated applications...
2. Remove all "Flexquarters QODBC" records
3. Close the preferences dialogs
4. Connect with your app, do NOT specify unattended mode
5. Close all applications using QODBC and make sure all the connections are closed.
6. Edit/Preferences/Integrated applications
7. Find your app, choose properties... and set unattended mode up for the user "admin"
8. Close preferences
9. Close QuickBooks
10. Run the application in unattended mode 

Yes, you can setup QODBC to use any QuickBooks user account you like:-

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. Use these settings to allow "auto-login" with or without a visable QuickBooks User Interface.

Some USA users may also find that auto-login doesn't work when they updated to QODBC v6.00.00.150 (or higher). To rectify this, simply follow the full 17 step procedure outlined in the original post at: After upgrading to QuickBooks 2006 or 2007, QODBC "auto-login" unattended mode no longer works? 

A DSNless connection like the one shown below needs to use auto-login mode by default to work correctly as it calls a company file.

Example of a DSNless connection string:
sConnectString = "Driver={QODBC Driver for QuickBooks};DFQ=C:\Program Files\QODBC Driver for QuickBooks\sample04.qbw;OpenMode=M;OLE DB Services=-2;"

To rectify your problem, please do the full 17 step procedure outlined in the original post at: After upgrading to QuickBooks 2006 or 2007, QODBC "auto-login" unattended mode no longer works? and use VB Demo and a normal DSN connection to correct the QuickBooks auto-login connection first with the other users on the network.

 Hi there,

I am getting this error code while trying to set up a DCOM server to run on our QBE machine.  I have been through the process outlined in this message several times, including the 17-step process listed in "After upgrading to QuickBooks 2006 or 2007, QODBC "auto-login" unattended mode no longer works" and have reached a roadblock.

I used the Automatic DCOM configuration code found in "Does QODBC work with MS SQL Server Linked Tables?" to set up my DCOM server.  I edited the VBS script to include permissions from my user account (with admin privs), the IUSR_<host> account and the ASPNET account.

I am getting a specific error when running TestDCOM.asp that I do not know how to resolve.  I suspect that this is the source of my 80040435 errors.   When running this script I see the message "Error: ActiveX component can't create object" on the XERCES-COM.dll row.   Everything else in the script's output is the same as shown in the message "How do I manually setup the QODBC DCOM Servers on Windows XP Pro and Windows 2003 Server?"

Any help on fixing this issue greatly appreciated!  Thanks.

_Mike

You also need to setup the security properties of the folder itself using Windows Explorer, not just the DCOMs:

Thanks for the fast reply.  I've confirmed the directory permissions to my QODBC Driver for QuickBooks directory and, for good measure, stopped and restarted IIS and am seeing the same results from TestDCOM.asp.

I also switched QBE running on my server's console from multi-user to single-user to make sure no new Integrated Application authorization popup occurred.  (It didn't.)

_Mike

Check your ActiveX settings for your browser:

No, my ActiveX settings are fine as I am running from the Intranet zone (connecting to localhost actually).

I checked the version of xerces-com.dll in case this might make a difference.  It is 2.6.0.0.

_Mike

OK, I've got the TestDCOM.asp script to work using the instructions found in the thread "QODBC and Windows Service".  Specifically, I changed the script to call Xerces.DOMDocument.2.5.0 instead of Xerces.DOMDocument.2.4.0.

However I still have my original problem regarding accessing QB through a DCOM connection.    For testing purposes, QB is running on the console in multi-user mode logged in as Admin.   I'm trying to connect to the System DSN for my QB instance from a Remote Desktop connection on the same Windows 2003 Server.

If I run VBDemo on the system console, it connects fine.  I'm assuming that DCOM isn't being used as it's connecting "locally".  If I exist VBDemo and then run it from a Remote Desktop connection (leaving QB running on the console), I get the following error in my QODBC Messages log:

IsAService: False
Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error = 80040435, Recent changes to your configuration require you (the QuickBooks Administrator) to go into the Integrated Applications preferences and re-authorize your integrated application to login automatically.
Begin Session errors can be caused when running ASP or other system service and not setting the "Advanced" button option of either "Use DCOM Servers" or "Remote Connector"

As previously stated, I've gone through the 17-step procedure to reset everything without success.

Thanks again for all the help and ideas.

_Mike

mstsc /v:servername /console