Troubleshooting: Begin Session Failed. Error = 8004041d, 80040418, 8004041a, 80040430,80042763

Problem Description:

Get the following errors from the QODBC driver:

ERROR [00000] [QODBC] QB Begin Session Failed. Error = 8004041d,80040418 This application is not allowed to log into this QuickBooks company data file automatically. The QuickBooks administrator can grant permission for automatic login through the Integrated Application preferences.

Test connection to QuickBooks - FAILED: "[QODBC] QB Begin Session Failed. Error = 8004041a. This application does not have permission to access this QuickBooks company data file. The QuickBooks administrator can grant access permission through the Integrated Application preferences." 

Problem Description:

I received the error: "Recent changes to your configuration require you (the QuickBooks Administrator) to go into the Integrated Applications preferences and re-authorize your integrated application to log in automatically." Immediately when starting the QODBC program.

Solutions:

Application integration authorization is required once per application for each Windows user. - http://qodbc.com/links/2785

Solution 1:

Step 1: Launch QuickBooks and Open the Company File

Open QuickBooks Desktop.

Log in to the desired company file using the QuickBooks user "Admin".

Log in to the QuickBooks user "admin" is required to authorize the connection to the QuickBookthe s company file.

This is a one-time activity for each new application you want to connect to QuickBooks Data.

Step 2: Test connection using QODBC 32-Bit Test Tool

Go to Start → QODBC Driver for QuickBooks → QODBC 32-Bit Test Tool.

In the QODBC Test Tool, 

Select DSN: QuickBooks Data

Click the "Connect" button.

QuickBooks may prompt you to authorize access: (optional)

If prompted, choose “Yes, always; allow access even if QuickBooks is not running”.

Select the Admin user from the dropdown (if applicable).

Click Continue → Done.

If the connection is successful, you can optionally run a test query (e.g., SELECT * FROM Customer).

Click "Disconnect" to close the connection.

Step 3: Test connection using QODBC 64-Bit Test Tool

Go to Start → QODBC Driver for QuickBooks → QODBC 64-Bit Test Tool.

In the QODBC Test Tool, 

Select DSN: QuickBooks Data

Click the "Connect" button.

This should successfully establish a 64-bit connection. You may not be prompted for permission as it has been granted in Step 2.

Once confirmed, click "OK" or "Disconnect" to close the session.

Step 4: Connect Using Your Application

In your application (e.g., PHP, .NET, Excel, Access, etc.), use the DSN name "QuickBooks Data" to establish a connection.

QuickBooks may prompt you to authorize access: (optional)

If QuickBooks does not ask for authorization, your application might already be authorized. You can run a few SQL statements/queries to verify that the connection is successful.

If you are unable to connect, please ensure you have logged in to the QuickBooks company file as the QuickBooks user "admin."

Note: If you use multiple applications with QODBC, you must perform Step 4 above for each application. 

Solution 2:

Please start the QuickBooks application and log in to your company file as QuickBooks user "Admin."

Switch to single-user mode.

Navigate to the "Edit" Menu -> "Preferences"  -> "Integrated Applications" -> "Company Preferences" Tab.

Please ensure ALL the "FLEXquarters QODBC" applications have the "Allow Access" option CHECKED/TICKED. If it is unchecked, please check it & apply changes by clicking the "OK" button.

Keep QuickBooks running and in single-user mode; try to connect with your application.

If you are still facing the issue, please remove all the integrated applications in QuickBooks via QuickBooks -> Edit Menu -> Preferences -> Integrated Applications -> Company Preference Tab.

How to remove QODBC Related Certificates from Integrated Applications under QuickBooks

After removing all the "FLEXquarters QODBC" integrated applications, please close the Integrated applications window.

Test the connection using QODBC Support Wizard and VB Demo.

Please Note: If you cannot connect to QuickBooks Data when a non-admin user is logged in to QuickBooks. You need to change the password of the non-admin QuickBooks user. For more information, please refer to Password security for QuickBooks Desktop.

Problem Description:

I have installed the latest version on a PC running Windows 2008 R2 and Reckon Enterprise 2014. I got the following message when I tried to test the link:

"QB Begin Session Failed. Error = 80040430, This application cannot log into the Reckon Accounts company data file automatically. The Reckon Accounts administrator must grant permission for automatic login through the Integrated Application preferences. If such permission was already granted, the administrator must revoke permission, then grant the permission again."

Solutions:

I want to inform you that the above error says that you have not accepted the QuickBooks certificate. Please keep QuickBooks running, log in as admin to your company file, Switch to single-user mode, and try to connect using your application. It should pop-up Data Access Certificate on QuickBooks, Please accept the integrated application certificate and try again.

Please create a new MS Access database & keep QuickBooks running, log in as admin to your company file, Switch to single-user mode, and try to connect. It should pop-up Data Access Certificate on QuickBooks. Please accept the certificate. 

I want to inform you that the QuickBooks issue Certificate is for each application. You might have accepted the certificate for application A, but application B would not have access. 

Notes for QB 2006 and before Users

For those who use QuickBooks 2006 and the previous version, please see: After upgrading to QuickBooks 2006, QODBC's "auto-login" unattended mode no longer works for more details on troubleshooting auto-login mode connections.

This is a known problem in the QuickBooks qbXML SDK from Intuit, caused by QuickBooks when upgrading an existing QuickBooks company file that had previously worked with QODBC to the new 2006 USA format (used by QuickBooks 2006 and 2007) or even adding new user accounts to QuickBooks. The problem still exists with QuickBooks 2007.

This issue is an Intuit SDK issue, not QODBC. Intuit required us to change unattended mode access for QuickBooks 2005 and 2006, which we did from QODBC v6.00.00.150 onwards. Unfortunately, all 2005 company files accessed previously by QODBC have this problem when the company file is converted by QuickBooks to the new 2006 or 2007 Anywhere Sybase backend format. The Intuit conversion corrupts the internal integrated applications settings, and you need to do the 17-step procedure workaround.

The staff at IntuitQBES (QuickBooks Enterprise Solutions) would like me to pass the following message to you:

Using the R5 (or later) release for QuickBooks Enterprise Solutions Version 8, developers can now use their QODBC applications with QuickBooks closed.

Download the R5 (or later)update here:

http://support.quickbooks.intuit.com/Support/ProductUpdates.aspx

Remember that when using this feature, you must use 'Locate a company file' or a QODBC connection string with "DFQ=C:\Program Files\QODBC Driver for QuickBooks\sample04.qbw" rather than 'Use the company file that's now open in QuickBooks.''

Note: R5(or later) for QuickBooks Enterprise 8 (2008) has the Intuit bug fix, not R11(or later) for QuickBooks Enterprise 7 (2007) !!!!

Problem Description:

The QuickBooks administrator must grant permission for an automatic login through the Integrated Application preferences. If such permission was already granted, the administrator must revoke permission, then grant the permission again.

Solutions:

The quickest way to fix this is to change the company file name.