Quickbooks Online credentials

[fhovey]

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/

[a_blue]

Hello! Are there any updates here, or does this issue still occur for other users?

[Warrenk]

I opened a ticket on this last month, and the short answer is that the issue is not resolved. I don't have confidence that this will be resolved anytime soon if I am being honest. This is part of the email response I got back after the ticket was closed:

"I would like to clarify the situation further. As mentioned, we have found a similar ICM (514347738) and we have received an update from our Product Group (PG) team and has confirmed that the issue you encountered is indeed "Bug - 1364063." and currently, the Product group recommended installing a Gateway as a workaround to remedy this issue. The Simba team is actively trying to resolve the issue. Because you do not have access to install the Gateway on your system, you stated that you will manually refresh data in Power BI Desktop until the issue is resolved. we aimed to be as transparent as possible in explaining this to you. However, we understand that your concern revolves around with this.

At this moment, I regret to inform you that there is no specific ETA for implementing changes to this . While I understand that this may not be the news you were hoping for, please rest assured that your feedback has been duly noted, and we will continue to thrive for improvements on your behalf. Our team is committed to enhancing our products and services based on valuable insights from customers like you."

[Warrenk]

Is an update available on this? The ODBC driver error persists using the Quickbooks Online connector when refreshing a published model.

[tamatha70]

Sadly, not that I have found, and I have posted this in several different forums here and in quickbooks but have yet to find any kind of answer besides the gateway workaround which isn't a solution for me.

[tamatha70]

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? 

[garylock]

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]

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?

[garylock]

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.

[DaveyL888]

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.

[garylock]

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

Thanks!

[fhovey]

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]

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!

[fhovey]

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

[DamienBI]

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]

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

[v-huijiey-msft]

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

[sushiservice]

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? 

[DaveyL888]

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

[ericspletzer]

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

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

[nickdc1]

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.