Hi, I have some reports in Powerbi that feed from my bd Mongo Atlas.
Since I update Mongo atlas to version 7.0, every day the automatic update fails, giving the following error:
Error: Request ID: 7e0991ee-241c-f944-3c9f-bb9a86ad10c5 Activity ID: ed795ed5-6bb5-4e3b-a435-53f4fb5a2ecc
This error appears in any of the collections that I have linked to my reports, randomly. If I launch the update again by hand, then sometimes it works the first time, and other times I have to relaunch the update because it fails again. But in any case, without doing anything on Mongo or Powwerbi or on the gateway I have set up, sometimes it works and sometimes it doesn’t. What can happen? Where can I see what real mistakes are happening? Thank you
hello @Mario_Gonzalez I am the Product Manager for the Power BI Connector.
If I understand correctly, your Atlas SQL Power BI connection is intermittent since you have upgraded your Atlas cluster to 7.0? Can you confirm this?
Where are you seeing this error? Is it within Power BI Desktop or the Cloud Power BI Service and the Gateway? Are you seeing the same result from PBI Desktop as the Service?
And I would definitely encourage you to have the latest version of our ODBC driver as well, which you can find here: Download Atlas SQL ODBC Driver | MongoDB
If you want to share more details privately, feel free to email me alexi.antonino@mongodb.com
Best,
Alexi
Hi Alexi,
yes, but no exactly: I have this error before upgrading mongo 7.0 but only somethimes (maybe once a week, or once every 2 weeks) .Since the upgrade, I’m seeing this error every day in Cloud Powerbi service (in its update log). I didn’t test it in PBI Desktop, because I don’t use it, only modeling the workspaces.
I’m using mongo odbc 1.4.3 yet, not Atlas SQL . The error occurs in Cloud Powerbi service.
Ok, i’m goint to update to the last version of mongo odbc (I just see that there ir a new version 1.4.5), but i dont understand why sometime works and sometimes doesn’t work , with doing no changes in the model and in the db.
I’ll share the results asap.
Thanks
Thanks for adding a bit more information. It is hard when things are intermittent. I would also suggest that we pull the ODBC logs and the Power BI Gateway logs as well. It might be some network bottleneck on the machine running the Gateway. Or I would look at the Atlas Network Access menu to make sure all traffic from the Gateway is in the list.