Problem Description

Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.

Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error = 80040408, Could not start Reckon Accounts.

Solutions

There can be multiple causes of the issue "Could not start QuickBooks." The common cause is QuickBooks, or your application is running in elevated user mode, or QuickBooks, which runs in two Windows user sessions.

If you use a service-based application such as ASP, ASP.NET, PHP, SQL Server, or Web Server with QODBC / QRemote - Please refer to solution number 3.

Solution 1:

Restart your machine. You need to restart your computer if you have recently installed or updated QuickBooks or installed QODBC.

Solution 2:

Your QuickBooks file should be accessible and not in the restricted folder.

Please start the QuickBooks application and log in to your QuickBooks company file as a QuickBooks Admin user. Try connecting to QuickBooks Data using your application.

If you still face the issue, please ensure that your QuickBooks is not running as "Run as Administrator."

Check "QBW32.EXE" using Task Manager.

Enable columns

Verify "QBW32.EXE" should not be Elevated - Yes.  

"QBW32.EXE" Elevated should be "No."

You can verify it by right-clicking the QuickBooks shortcut, going to "Properties," & navigating to the "Compatibility" tab & make sure that the "Run this program as an administrator" option is unchecked. If this option is enabled, then please disable it & apply the changes.

Click "Change settings for all users" and verify that "Run as Administrator" is not selected.

Right-click on the QuickBooks application shortcut from the desktop

Make sure "Run as Administrator" or "Run this program as an Administrator" is unchecked.

Click Change settings for all users.

Ensure "Run as Administrator" or "Run this program as an Administrator" is unchecked.

Please navigate to the QuickBooks folder under program files.

Right-click on QBW32.exe and other QuickBooks applications that start with QBW32

Ensure "Run as Administrator" or "Run this program as an Administrator" is unchecked.

Click Change settings for all users.

Ensure "Run as Administrator" or "Run this program as an Administrator" is unchecked.

Please restart the Close QuickBooks application and restart your machine.

After restarting, please start QuickBooks and log in to your QuickBooks company file as a QuickBooks Admin user.

Optional - You may switch to single-user mode.

Try connecting with your application.

Solution 3:

If you are using a Web Application, SQL Server, IIS, PHP, or Service application, Windows Scheduler, or PowerShell from a scheduler, please use QRemote DSN

• QODBC Desktop - "QuickBooks Data QRemote" or "QuickBooks Data 64-Bit QRemote."
• QODBC Online - "QuickBooks Online Data QRemote" or "QuickBooks Online Data 64-Bit."
• QODBC POS - "QuickBooks POS Data QRemote" or "QuickBooks POS Data 64-Bit."

If you still face the issue, please try connecting to QuickBooks using QODBC Support Wizard. 

Solution 4:

QODBC and QuickBooks Auto Login:

If you are trying to run QODBC/QuickBooks in auto-login? And is your machine having Terminal serviced/remote desktop enabled? i.e., multiple users logging into your machine using the Remote desktop connection. Then, I would like to inform you that QuickBooks SDK has a known issue with this type of Environment setup and cannot start QuickBooks in the background. (If more than one user is logged into the machine and QBW32.exe runs on more than one user account). 

Workaround for the above issue.

1) Ensure you unselect the "Keep QuickBooks running for quick start-up" option under QuickBooks -- Edit Preferences -- General.
Close all other QuickBooks instances of all other users and then try. (Please verify no instances are running of QBW32 under task manager --processes -- view all user processes)

Also, please verify the company file path on QODBC and QuickBooks. These two paths should be the same. The QODBC company file path can be found via the QODBC setup screen -> General tab.

You can find the QuickBooks company file via QuickBooks UI. Press the F2 key, and you will see the file information.

You can also use the QODBC Support Wizard on the QuickBooks machine and check the elevated status of QuickBooks. The Elevated check should be green.

Please refer to How to use QODBC Support Wizard
http://qodbc.com/links/2981

Either you can verify it by the below steps. 
Please right-click on Taskbar and open Task Manager.
Navigate to the Details tab.
1) Right-click on the first row and click on 'Select Columns'.
2) Check the 'Elevated' and 'Platform' columns.
3)Verify the status of QBW32.EXE

If QBW32.EXE elevated status as 'Yes,' you must run the QuickBooks UI under the non-elevated user context.

Please refer to How to remove elevated mode from QuickBooks
[Section - Solution 2]


Start QuickBooks and log in to the QuickBooks company file as QuickBooks user "Admin".
Connect to QuickBooks Data using the QODBC 32-bit Test Tool.
Disconnect.

Log off from the QuickBooks company file. Keep the QuickBooks application running.
Connect to QuickBooks Data using the QODBC 32-bit Test Tool.
This should auto-login to the QuickBooks company file.
Disconnect.
This should auto-log off from the QuickBooks company file.

Close the QuickBooks application.
Connect to QuickBooks Data using the QODBC 32-bit Test Tool.
This should auto-login to the QuickBooks company file.
Disconnect.
This should auto-log off from the QuickBooks company file.

If you are able to use auto-login when using the QODBC Test Tool but not with your application, then your application might not be running in normal mode. It might run in "Run as Administrator" - i.e., Elevated Mode. Start your application in normal mode and try again.

Another possibility is your application is running as a "Service" or in a different user profile. In this case, you will have to use "QRemote" DSN. Please connect to "QuickBooks Data QRemote" or "QuickBooks Data 64-Bit QRemote". Please ensure the QRemote Server runs on the same Windows instance/profile where QuickBooks is running, and "QRemote Server" should not be in "Elevated" mode.

Solution 5:

You can select "Use the Company file that's open in QuickBooks" and test again.

OR

2) Keep QuickBooks running (No need to login to the company file; keep the QuickBooks window open) and try connecting

OR

3) For QODBC 13.0.0.291 and upwards, under the Advanced tab, enable "Force Start QuickBooks," Make sure you unselect the option of "Keep QuickBooks running for quick start-up" under QuickBooks -- Edit Preferences --, General

If QuickBooks is already open and you are getting this error, please ensure you are not running Your Application in an elevated user context, i.e., you should not run it as "Run as administrator." 

Additional Information:

20140321.113817 I 3404 RequestProcessor Connection opened by the app named 'FLEXquarters QODBC.'
20140321.113817 I 3404 CertVerifier The Authenticode signature validated OK.
20140321.113817 I 3404 RequestProcessor OS: Microsoft Windows Server 2008 R2 Datacenter Edition Service Pack 1 (build 7601), 64-bit
20140321.113817 I 3404 RequestProcessor Current Process is elevated
20140321.113817 I 3404 RequestProcessor Current User is in AdminGroup
20140321.113817 I 3404 RequestProcessor Current Process is run as Admin
20140321.113817 I 3404 RequestProcessor Current Process Integrity Level: 3000
20140321.113817 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113818 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113818 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113819 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113819 I 3404 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20140321.113820 E 3404 RequestProcessor Could not find or create an instance of QuickBooks using InstanceFinder
20140321.113820 I 3404 RequestProcessor Connection closed by the app named 'FLEXquarters QODBC.'
20140321.113820 I 3404 RequestProcessor ========== Ended Connection ==========

Solution 6:

This shows that your app is running under elevated permission. Try fixing the permissions and see if that resolves the issue. QB and the app must be running at the same level, either as the standard user or using Run As Admin. They cannot be mixed.

This also happens when more than one user is logged in (and has QBW32.exe running in the user process) to the machine using (a remote desktop connection) and trying to run QuickBooks with auto Login. QuickBooks SDK shall not be able to find the instance in such a case. A workaround is to keep QuickBooks running. No need to log into the machine. Just keep the window open.

Refer:

https://intuitpartnerplatform.lc.intuit.com/questions/834524-failure-to-connect-to-qb-13-after-update-could-not-find-or-create-an-instance-of-quickbooks-using-instancefinder

https://intuitpartnerplatform.lc.intuit.com/questions/805619-getting-error-2147220472-could-not-start-quickbooks

http://stackoverflow.com/questions/20905010/getting-error-2147220472-could-not-start-quickbooks

https://intuitpartnerplatform.lc.intuit.com/questions/817461-could-not-find-or-create-an-instance-of-quickbooks-using-instancefinder

Keywords: 80040408, autologin