Can't publish a model after using OneDrive refresh fails

[fmaturanav]

I'm using the feature to publish a report using the OneDrive/SharePoint import method.

After using this method for a while without issues, one day a user overwrote the PBIX file, and the changes stopped being published.

Here’s what I’ve tried:

1. Publishing from Power BI Desktop (it says it can't because the report is published via the OneDrive method).
2. Disabling the OneDrive auto-update and enabling it again.
3. Disabling the OneDrive auto-update and trying to publish from Power BI Desktop (same error as step 1).
4. Publishing again using the same method — this created a new semantic model and report, resulting in duplicate reports.
5. Using the "Import from this computer" option (same error as step 1).
6. Publishing again using PowerShell (same error as step 1).
7. Restoring a previous version of the PBIX file.

here is the documentation.

https://learn.microsoft.com/es-mx/power-bi/connect-data/refresh-desktop-file-onedrive#automatic-vers...

[v-tejrama]

Hi  @fmaturanav ,

This issue typically occurs when a PBIX file that was originally published to the Power BI Service using the OneDrive or SharePoint “Import” connection becomes disconnected from its source file. When a report is published this way, Power BI maintains a direct link between the semantic model in the service and the specific file path in OneDrive. If that PBIX file is later replaced, moved, or renamed, Power BI can no longer recognize it as the same file. That’s why you’re seeing the “OneDrive for Business error while accessing the file” message and why republishing from Desktop results in a new dataset rather than updating the existing one.

To resolve this, first confirm that the PBIX file in OneDrive or SharePoint hasn’t been renamed or replaced. If it has, revert it to its original path or restore it from version history, and make sure it’s stored in a shared document library that your Power BI workspace can access. Then download the PBIX directly from the Power BI Service so you’re working with the version Power BI currently recognizes. Open it in Power BI Desktop, check your data source settings to ensure the connection still points to the same OneDrive or SharePoint location, and sign out and back in to refresh your credentials. When you publish again, choose the overwrite option so Power BI can correctly re-establish the link to the original semantic model.

If publishing still fails, it’s best to remove the existing dataset and report in the service and then publish the PBIX fresh from Desktop. Going forward, avoid replacing the PBIX file manually in OneDrive and instead let Power BI handle updates. In rare cases where the issue persists, the problem could be with the tenant’s OneDrive integration token, which an admin can reset from the Power BI Admin Portal under OneDrive and SharePoint Integration settings.

You can also refer to Microsoft’s official documentation for guidance on refreshing Power BI files from OneDrive or SharePoint, publishing from Power BI Desktop, and troubleshooting dataset refresh errors.Once the file paths are properly aligned, your report should publish and refresh normally again.

You can also review the official Microsoft documentation below, which covers this exact scenario:

• Refresh a Power BI Desktop file from OneDrive or SharePoint Online

• Publish from Power BI Desktop to the service

• Troubleshoot dataset refresh errors

Once the PBIX and OneDrive file paths are properly synced, the auto-update feature will resume as normal, and you’ll be able to publish or refresh without needing to recreate the report.

Thank you,

Tejaswi.