Domo Workbench will not connect to Quickbooks after authorizing.

Multiple jobs were setup by an employee who is no longer at the company. I have removed Domo Workbench from integrated applications on Quickbooks and then reauthorized for every job. It worked yesterday and now will generate this error every time I run the job (manually or scheduled).
"This application is unable to log into this QuickBooks company data file automatically. 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, save preferences, then grant the permission again."

I've confirmed no users are logged in when executing. I've deleted workbench and re-authorized the job and the account multiple times. What am I missing?

Answers

  • Just like the error says - in the Integrated Applications you need to make sure Domo has the ability for automatic login, and if you do, revoke it, save it, re-add it back in.

    Quickbooks desktop gets real weird with authentication, best practices is have an account just for the Domo integration, but it needs to login to QBs when there's already another account logged in but not the max accounts. It can get kinda hairy.

  • Hi @TaraW

    I would agree with everything @trafalger says here, and also take a look at this thread for some other issues that might be causing you trouble as there are some specific policies you want to ensure are applied in Windows for the Quickbooks Desktop / Workbench integration to function correctly:

    User not a member of the 'Domo Workbench User' - But only when using impersonation — Domo Community Forum

    You may also want to open a Domo Support ticket on this as this particular setup (QB Desktop & Workbench) can be a bit tricky to get right.

  • I would suggest logging into Quickbooks as admin. Make sure the user has full access to the company with no restrictions. Remove Domo Workbench. Restart QuickBooks and retrigger the authorization process again.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **