Knowledgebase: Tutorials
[QODBC-Desktop] Troubleshooting - Changes to the Integrated Application Authentication for QuickBooks
Posted by Jack - QODBC Support on 21 June 2016 03:21 PM

Troubleshooting - Changes to the Integrated Application Authentication for QuickBooks

Intuit is reinforcing existing security features that help protect QuickBooks customers’ sensitive information.
Refer: Intuit's News: Changes to the Integrated Application Authentication for QuickBooks Desktop users


As a result of this effort, Intuit is delivering an update that impacts third-party applications that connect to QuickBooks using the QuickBooks SDK.

A new file specific to a Windows user on a given machine is created on user login that provides access to an SDK app in QuickBooks.

The implementation of this update will require customers to re-enter their login-in credentials & authorize the application(i.e., QODBC) at QuickBooks.

For Example, You have four windows users. All those four windows users use QODBC via Microsoft Excel, Access, Crystal, or other applications. You will need to authorize EACH application from all 4 Windows users. That means you will need to login to the 1st windows user, endorse all the applications that will be using QODBC, then login to the 2nd Windows user and authorize all the applications that will be using QODBC. This is because Intuit's LGB file, which was common earlier, is now changed to a new method, and integration information will be stored for each Windows user separately.

The above is applicable for a Single machine, Terminal Services(Remote desktop connection), or Workstation(s).

Problem Description:

Get the following errors from the QODBC driver:

ERROR [00000] [QODBC] QB Begin Session Failed. Error = 8004041d,80040418 This application cannot 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 Quick Books - 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."

Step.png

Error.png

Solution:

You need to follow the below steps to reauthorize QODBC for QuickBooks.
1. log in to Windows, Open QuickBooks & log in to the company file as Admin.
2. Switch Company File to Single User Mode.

3. Connect using your application. It should pop-up Data Access Certificate on QuickBooks, Please accept the Certificate. QuickBooks issue a Certificate for each application, So you need to get the Certificate for all application that you use with QuickBooks.

4. You must log in to each Windows user accessing QuickBooks Data using QODBC.
If Windows User/Work Station changes, you must reauthorize the application using the above steps.

If the company file has Personally Identifiable Information (PII) in QuickBooks, users must log in with a password; the SDK app will only be allowed to connect once the login has been completed for that user. 

Customers will be instructed to set up a strong password when logging in. Customers should use unique letters and numbers in a password, not essential words that can easily be found online or in the dictionary.

(4 vote(s))
Helpful
Not helpful

Comments (8)
Sandip Laxman Dahihande
09 February 2017 06:07 AM
I have tried above steps but still QuickBooks Enterprise Edition 2017 asked for Login into QuickBooks again and again. Please help
Jack
09 February 2017 06:44 AM
Hi Sandip,

Please make sure that you have accepted the certificate for each Windows Users who is accessing QuickBooks Data using QODBC.

If Windows User/Work Station changed, then you need to reauthorize application.

If QuickBooks is asking certificate for same application for same Windows user which you accept earlier, then I kindly suggest refer below mentioned link & follow steps:
http://support.flexquarters.com/esupport/index.php?/Knowledgebase/Article/View/2406/60/connection-lost-between-qodbc-and-quickbooks-quickbooks-asking-for-password

If you are still facing the issue, I kindly request you to please raise a support ticket to the QODBC Technical Support department from below mentioned link & provide requested information:

http://support.flexquarters.com/esupport/index.php?/Tickets/Submit

We may need the following information, I kindly request you to attach below listed files when replying to the ticket.
1) Screenshot of QODBC Setup Screen -- > About
2) Screenshot of the issue you’re facing.
Share Entire Log Files as an attachment in text format from
3) QODBC Setup Screen -- > Messages -- > Review QODBC Messages
4) QODBC Setup Screen -- > Messages -- > Review SDK Messages
Dat Nguyen
14 April 2017 08:14 AM
Is there any way let user Accept certificate once and trust an app, so the app can access to new opened company file automatically.
Jack
14 April 2017 01:39 PM
Hi Dat,

Certificate process is handled by QuickBooks and not by QODBC. QODBC doesn't have control of the QuickBooks certificate process.

You need to login to company file as Admin into QuickBooks & accept the certificate. Only Admin privileges user in QuickBooks can accept the certificate & this activity only once per application & Windows User. You need to log in for each Windows Users who is accessing QuickBooks Data using QODBC.

If QuickBooks find that some issue in app certificate, then it may ask for accepting certificate again.
Sanya
15 June 2017 07:38 PM
I have a process which copies the new version of the quickbook file every month from another server and extracts data from it using QODBC but I need to give access to the driver everytime. Is there some way I can automatically grant permission?
Jack
16 June 2017 01:35 PM
Hi Sanya,

I'm sorry to inform you that the automatically grant permission feature is not available through the Intuit SDK so they are not available through QODBC.

QODBC is an ODBC driver for QuickBooks. It uses the QuickBooks SDK to communicate with QuickBooks, which means if Intuit doesn’t expose one feature to the application in SDK, QODBC could not do it either.

Please refer:
http://support.flexquarters.com/esupport/index.php?/Knowledgebase/Article/View/2717
mary moran
27 July 2017 12:46 PM
I've verified that QODBC is connected but when I go to run my access database I get a generic message that access has stopped working.

any suggestions?
Jack
28 July 2017 03:33 AM
Hi,

For Office 365 crash issue. MS Office is not allowing to write to the registry and thus QODBC throws this error. Please run the patch or follow the manual steps from below mentioned link:
http://support.flexquarters.com/esupport/index.php?/Knowledgebase/Article/View/2718

If you are still facing the issue, Please raise a support ticket to the QODBC Technical Support department from below mentioned link & provide requested information:
http://support.flexquarters.com/esupport/index.php?/Tickets/Submit

We may need the following information, I kindly request you to attach below listed files when replying to the ticket.
1) Screenshot of QODBC Setup Screen -- > About
2) Screenshot of the issue you’re facing.
Share Entire Log Files as an attachment in text format from
3) QODBC Setup Screen -- > Messages -- > Review QODBC Messages
4) QODBC Setup Screen -- > Messages -- > Review SDK Messages
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please complete the captcha below (we use this to prevent automated submissions).