Forum Discussion
error while publish to the service
Dears,
anybody knows anything about this error ?
This is a generic publish failure while pushing a PBIR/Project (“definition.pbir”). It usually happens due to a transient service issue, an outdated Desktop build, or a PBIR project bug. Try these quick fixes in order:
-
Update Power BI Desktop to the latest build, then retry.
-
If you opened a Power BI Project (.pbip), export to a .pbix (File > Export > Power BI Desktop (.pbix)) and publish the PBIX instead. PBIR publish is flaky.
-
Publish to a different workspace (not “My workspace”) and make sure you’re Member/Contributor.
-
Sign out/in; clear cache (Options > Data Load > Clear cache) and clear credentials (Data source settings).
-
Try a different network or disable VPN/proxy; check status.powerbi.com for outages.
-
Remove special characters/very long paths from the report name or folder and retry.
Still failing? Turn on tracing (Options > Diagnostics), reproduce the publish, and share the latest trace with Support along with the Session ID shown in the dialog.
-
2 Replies
- rohit1991Super User
This is a generic publish failure while pushing a PBIR/Project (“definition.pbir”). It usually happens due to a transient service issue, an outdated Desktop build, or a PBIR project bug. Try these quick fixes in order:
-
Update Power BI Desktop to the latest build, then retry.
-
If you opened a Power BI Project (.pbip), export to a .pbix (File > Export > Power BI Desktop (.pbix)) and publish the PBIX instead. PBIR publish is flaky.
-
Publish to a different workspace (not “My workspace”) and make sure you’re Member/Contributor.
-
Sign out/in; clear cache (Options > Data Load > Clear cache) and clear credentials (Data source settings).
-
Try a different network or disable VPN/proxy; check status.powerbi.com for outages.
-
Remove special characters/very long paths from the report name or folder and retry.
Still failing? Turn on tracing (Options > Diagnostics), reproduce the publish, and share the latest trace with Support along with the Session ID shown in the dialog.
- ahmedshalabyy12Helper V
Clearing the cache solution worked thank you it was size issue
-