Knowledgebase: TroubleShooting
[QODBC-Desktop] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks
Posted by Rajendra Dewani (QODBC Support) on 26 December 2013 09:43 AM

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.

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"

Solutions

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

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

If you are still facing the issue, Please make sure that your QuickBooks is not running as "Run as Administrator". You can verify it by right-clicking QuickBooks shortcut, go to "Properties" & navigate to "Compatibility" tab & make sure that "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", verify that "Run as Administrator" is not selected.

Right click on QuickBooks application shortcut from the Desktop

http://support.flexquarters.com/esupport/newimages/2018-10-31-17_06_25-QuickBooks.png

http://support.flexquarters.com/esupport/newimages/2018-10-31-17_06_26-QuickBooks-Properties.png

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

http://support.flexquarters.com/esupport/newimages/2018-10-31-17_03_18-QuickBooks.pngClick Change settings for all users.

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

http://support.flexquarters.com/esupport/newimages/2018-10-31-17_03_51-QuickBooks.pngPlease navigate to the QuickBooks folder under program files.

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

http://support.flexquarters.com/esupport/newimages/2018-10-31-16_54_22-QuickBooks.png

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

http://support.flexquarters.com/esupport/newimages/2018-10-31-16_54_52-QuickBooks.png

Click Change settings for all users.

 

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

 

http://support.flexquarters.com/esupport/newimages/2018-10-31-16_54_58-QuickBooks.png

 

Please restart Close QuickBooks application and restart your machine.

After restart please start QuickBooks and login to your QuickBooks company file as QuickBooks Admin user.

Optional - You may switch to single user mode.

Try connecting with your application.

 

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

 

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 user 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 the QuickBooks in the background. (If more than one user is logged into machine and QBW32.exe is running on more than one user account). 


Workaround for the above issue.

1) Make sure you unselect the option of "Keep QuickBooks running for quick start-up" 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. You can find QODBC company file path via QODBC setup screen -> General tab.

You could find the QuickBooks company file via QuickBooks UI, press F2 key you will see the file information.

OR

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 company file, just keep 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 then please make sure you are not running Your Application in elevated user context, i.e. you should not run it as "Run as administrator".
 

Additional Information:

20140321.113817 I 3404 RequestProcessor Connection opened by 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 ran 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 app named 'FLEXquarters QODBC'
20140321.113820 I 3404 RequestProcessor ========== Ended Connection ==========

Solution:

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

This also happens when there is more than one user logged in (and has QBW32.exe running in user process) to the machine using ( remote desktop connection ) and trying to run QuickBooks with auto Login.  QuickBooks SDK shall not able to find the instance in such case.  A workaround is to keep QuickBooks running, No need to login to 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 : 80040418, autologin

 

(2 vote(s))
Helpful
Not helpful

Comments (6)
Eddie Falkenburg
29 May 2014 05:41 PM
Will there soon be a fix for multi-user environments? We are able to get around the problem with the suggested workarounds, but it presents more failure points that we would like to remove eventually.
Jack
07 July 2014 12:57 PM
Hi Eddie,

I would like to inform you that this is known issue with QuickBooks SDK (In Multiuser Environment setup and cannot start the QuickBooks in background.) not with QODBC.

I would like to inform you that recently QuickBooks has fixed this issue on QuickBooks 2014 R6.

Fixed an issue that caused QuickBooks to close when duplicating a transaction after a menu item is added through the SDK.

Fixed an issue that caused the error “Could not find or create an instance of QuickBooks using InstanceFinder”, when connecting to QuickBooks while it is not running in UI.

Please refer below mentioned link for more information:
http://support.quickbooks.intuit.com/support/articles/inf24723

So you may try QuickBooks 2014 R6 or above version.
Patrick
29 September 2015 07:21 PM
We are still running into this problem on QB Manufacturing and Wholesale 2015 R6P. Is it possible that this has not been addressed in this version and build?
Jack
30 September 2015 09:56 AM
Hi Patrick,

To know whether issue resolved in QuickBooks or not. You should refer release note of QuickBooks.
Al Buchholz
13 July 2016 05:40 PM
Jack

Please provide a link or navigation directions to the release notes that you are referring to.

Thank you.
Jack
13 July 2016 06:22 PM
Hi Al,

You need to get in touch with Intuit for QuickBooks release note.
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please complete the captcha below (we use this to prevent automated submissions).