Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
fhovey
Advocate I
Advocate I

Quickbooks Online credentials

I'm logged into quickbooks online on Power BI desktop just fine and everything refreshes. I published it to my workspace and went to set an autorefresh and it asked me to log into QBO. I logged in but then I get this error message. It's the same credentials from the desktop. Does anyone know how to fix this? Thanks!

 

Failed to update data source credentials: ODBC: ERROR [IM004] [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failedHide details

Activity ID:1c8e67db-60c0-4056-90f5-3efe6e5afa5c
Request ID:4601c7a8-e9be-cec4-4eb5-36e26c348c64
Status code:400
Time:Fri Mar 01 2024 17:46:48 GMT-0500 (Eastern Standard Time)
Service version:13.0.22729.74
Client version:2402.3.18145-train
Cluster URI:https://wabi-us-north-central-b-redirect.analysis.windows.net/
26 REPLIES 26
tamatha70
Regular Visitor

It is July and I am experiencing the exact same problem. Works when I refresh from desktop BI, I can successfully update my credentials by signing into quickbooks but get the error : Failed to update data source credentials: ODBC: ERROR [IM004] [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed"

Is there a solution that is not the on-premise gateway workaround yet? 

FYI - The on-premises gateway workaround is very unreliable. It appears the issue is on the QuickBooks side, but refreshes are very inconsistent. The same semantic model can take 2 minutes to refresh on one day, then spin for 2 hours and time out the next day. Unfortunately, we may need to go the API route for our QB data.

garylock
Frequent Visitor

Any update from Microsoft on this issue? @v-huijie-msft 

 

Ideally, the Power BI QuickBooks Online connector could get fixed and be moved out of beta.

 

However, as a workaround I am trying to implement the on-premises data gateway solution.

 

As a test, I downloaded the gateway onto my laptop and was able to set up QuickBooks Online connections without issue.

 

For my client, we created a new VM in Azure running Windows Server Datacenter 2022 and installed the on-premises data gateway onto the new server with nothing else installed on the server.

 

The gateway installed fine, and all the Simba Quickbooks ODBC Driver files appear to be in order. The gateway also shows as Online in the Power BI Service.

 

Unfortunately, when I try setting up a new QuickBooks online connection, I get the usual ODBC error:

ODBC: ERROR [IM004] [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

 

What else needs to be installed on the server to get the gateway to run properly for the QuickBooks Online connection?

 

On my personal laptop, I have SQL Server 2022 installed and the ODBC Driver 17 for SQL Server. I tried installing both on the new server, but it did not help the gateway issue.

 

At this point, I cannot think of anything else to try. I am hoping to get some help from the Microsoft team?

 

 

In case anyone is running into issues trying to use the on-premises data gateway solution, I figured out how to get the QBO connections to work.

I had a new server with Windows Server 2022 Datacenter running on it and was still getting the "Driver's SQLAllocHandle on SQL_HANDLE_ENV failed" error.

 

After installing Visual Studio 2022 Community on the server I am now able to set up QBO connections on the gateway. I don't know exactly which component of VS resolved the issue, but figured I'd share.

Experiencing the same issue, I have had to log a ticket with Microsoft - Power Platform admin center; we are currently working through this issue with them.

 

I have a booking next week to continue the troubleshooting and they have given information that this is still an ongoing issue as other users in the powerbi community have also reported the issues as well and they are needing as much information as possible to put to QB to determine where the fault lies.

 

I feel like there is some kind of token auth time out issue in the cloud connector and this is possibly blocking the session as this is not an issue when the desktop client establishes a connection.

Hey @DaveyL888 , any luck this week with the Microsoft team?

 

Thanks!

fhovey
Advocate I
Advocate I

We put in a ticket in with microsoft in the beginning of March and we still don't have a solution. We were told to wait while they develop a solution. 

v-huijiey-msft
Community Support
Community Support

Hi @fhovey  @a_blue ,

 

It is been a while! There is a new development on the issue.

 

@DamienBI answered the related question and his related efforts are much appreciated.

 

Please try this solution to see if it works.

 

If you have any other questions please feel free to contact me.

 

Best Regards,
Yang
Community Support Team

 

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

This solution did not work for me. I don't have an ODBC Quickbooks driver

DamienBI
Frequent Visitor

Hi,

 

I've found a fix for this using the on premise gateway. but will probaby work for personal gateways.

Find where your power BI desktop is installed and go to the ODBC Drivers folder. For me is was "C:\Program Files\Microsoft Power BI Desktop\bin\ODBC Drivers" however this may be different for you if you have the windows store version.

 

Copy the folder named "Simba Quickbooks ODBC Driver" (I made a zip file from this folder as we need to copy this to where the gateway is installed)

 

On the machine where your gateway is installed, go to "C:\Program Files\On-premises data gateway\m\ODBC Drivers\" (Again will be different for personal gateways). Delete the folder named "Simba Quickbooks ODBC Driver" then paste/extract the one we copied earler.

 

Hope that helps!

a_blue
New Member

I've had this issue the 1st too. Still unresolved!

v-huijiey-msft
Community Support
Community Support

Hi @fhovey , 

 

This issue has been confirmed as a known issue internally. Please be patient to wait for fixing. If there is any news, I will update it here.

 

Best Regards,
Yang
Community Support Team

This is still an unresolved issue. It has been over a month. Do we have any updates? @v-huijiey-msft ?

@fhovey - Please mark this conversation as unresolved as Yang's comment is not a solution. The on-premise gateway suggestion is a bad workaround and should not be suggested. The community needs to come together to rise these important bugs up to Microsoft. 

Here are my error details:

- I can confirm the connection to QBO works still using Power BI Desktop. 
- I have deleted the existing dataset in Power BI Service and re-published under a different dataset name to see if that would help, it did not. 
- I have tried multiple variations of selecting (None, Private, Public, Organizational under OAuth Connection Settings and they all do not work) 

Failed to update data source credentials: ODBC: ERROR [IM004] [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

@quickbooks @Quickbookpro @Quickbooksorg Maybe you can help here? 

Same issues on my end, online powerbi reporting refresh will not work but the desktop powerbi will work no problems. 

 

And all the credentials are correct!

 

Failed to update data source credentials: ODBC: ERROR [IM004] [Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

I am having this same issue.  Is there any word?

It renders a lot of our financial reporting very difficult to use.

 

I have been having this issue, and using the information here have managed to work around it using a local gateway.

 

The issue is specifically connected to creating new QuickBooksOnline connections in the cloud. This connector still works fine in Power BI Desktop, and if you are using the (I think previous) QuickBooks (rather than QuickBooksOnline) connector - which can connect to QuickBooks Online - that still works in the cloud too.

 

To get this to work, I installed an on premise gateway and then created a new QuickBooksOnline connection with it. While this was successful, I now got a new error while refreshing the dataset I'd assigned this connection to.

 

To resolve this, I changed one of the Gateway options to allow "Allow user's cloud data sources to refresh through the gateway cluster" and this now seems to work fine. 

 

It is unclear why this connector has broken and whether it's a Microsoft or Intuit issue. It makes me rather concerned, as if the local connector option breaks then we're out of options for syncing this financial data.

v-huijiey-msft
Community Support
Community Support

Hi @fhovey ,

 

When using the Power BI service for automatic refresh, please ensure that the Power BI gateway is installed and correctly configured.

 

The gateway acts as a bridge between on-premises data and cloud services. It is essential for refreshing data sets that are not directly connected to cloud services.

 

The steps are as follows:

 

Select the gear icon in the upper right corner.

vhuijieymsft_0-1709519361118.png

 

Click new in the upper left corner to configure data source information.

vhuijieymsft_3-1709519428440.png
vhuijieymsft_4-1709519428440.png

 

After the configuration is complete, go to the workspace and select semantic model.

vhuijieymsft_5-1709519455844.png

 

Check that the information for the two options below is correct.

vhuijieymsft_6-1709519455845.png

 

For more information on setting up and configuring your gateway, please see:

Manage your data source - import and scheduled refresh - Power BI | Microsoft Learn

 

When setting up dataset refresh in the Power BI service, make sure you select the correct authentication method for QuickBooks Online.

 

Edit the dataset settings in the workspace to verify and update this information.

 

If you have any further questions please feel free to contact me.

 

Best Regards,
Yang
Community Support Team

 

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

This is a work-around....but not a solution.  This is supposed to refresh in the cloud, not on a local on premise gateway.

Hi. Im having the same issue as this however my has been working previously for 2+ years and has only in the last week or 2 started getting this error. Nothing has changed my side. I didn't have to use a gateway previously but I have also tried with our gateway and it still doesn't work.

Thanks

I got this error when trying to sign in after setting up the gateway

 

fhovey_0-1709583543952.png

 

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.