The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
hello!
I have a report/project shared in one drive.
We changed the server updating the OS from 2016 to 2022.
on the 2016 everything worked fine, now, with 2022, I have this error while I'm opening the project in PowerBI desktop.
the same project in a windows 11 (updated from 10 to 11) virtual machine, in the same server works without any error.
I created a totally new windows 11 machine in the same server and it doesn't work.
I tried to open the project in another 2016 updated to 2022 and it doesn't work.
The report works fine in the service and updates without any issue.
I have already installed the last version of powerbi desktop, the last (and previous) version of the ODBC driver.
The configuration is the same in all the machines.
I've already checked every origin and they are all ok...
I don't really know how to fix this problem
This error (file '', line, function '') isn’t caused by the PBIX file itself it’s almost always due to an environment issue. Since it works on one machine and not others (all with different OS setups), the root cause is likely one of the following:
Corrupt or incompatible ODBC/OLEDB drivers (even if updated)
Permissions or access issues from OneDrive/shared paths
Missing dependencies after OS upgrade (like .NET or C++ runtimes)
Fix to try:
Move the file to a local folder (e.g., Documents)
Run Power BI as Admin
Try Compatibility Mode (set to Windows 10)
Fully uninstall and reinstall the ODBC driver
Check Event Viewer or %LOCALAPPDATA%\Microsoft\Power BI Desktop\Temp\ for detailed error logs
If none of that works, it's worth logging a ticket with Microsoft this seems like a system-level bug post-upgrade.
Hello @eugenio_paoli,
Thank you for reaching out to the Microsoft Fabric Community and providing detailed information about the issue. Here are some troubleshooting steps to try:
Thank you @lbendlin, for sharing valuable insights.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
thank you for your support!
Hello @eugenio_paoli,
Just checking in have you been able to resolve this issue? If so, it would be greatly appreciated if you could mark the most helpful reply accordingly. This helps other community members quickly find relevant solutions.
Please don’t forget to “Accept as Solution” and Give “Kudos” if the response was helpful.
Thank you.
unfortunately not solved yet! 😞
Hello @eugenio_paoli,
We regret the inconvenience caused. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.
You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this helps, please accept it as a solution and drop a "Kudos" so other members can find it more easily.
Thank you.
Hello @eugenio_paoli,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding.
Microsoft are listing this issue on their admin center. Service health - Microsoft 365 admin center (if you have access)
As a workaround, users with the Power BI Report Server May 2025 version can move back to the January 2025 version. Users with Power BI desktop can use the 32-bit May 2025 version or they can move to the previously released version.
thank you!