Forum Discussion
PBIP Publishing failed for an unknown reason
When trying to publish a pbip file I get an error that 'Publishing failed for an unknown reason.' It uses a live connection to a semantic model in the same workspace I am trying to publish to, but that semantic model is also a pbip file that gives the following message when published.
I am wondering if this is because I am publishing to a Power BI service WS and not a Fabric WS? I am on a government license, so I don't have access to Fabric.
Got it working! It looks like it is just the PBIR format that is not supported for Gov license. Turned that off and now it saves and publishes with no issues.
6 Replies
- MasonMA
Super User
Hello MaBERG
As previous user mentioned, this might be a restriction from your government cloud. You may need to verify with your IT Admin.
You may also consider using its converted PBIX file if this is possible and recreate the report’s Live Connection to point to this published dataset.
We are also on government cloud and I've seen same error as yours a few times with PBIX file after they get published to workspaces. For PBIX file in our case this is usually caused by cloud gateway that was not properly set up by Platform team.
Hope this helps:)
Hi MaBERG
Thank you for reaching out to the Microsoft fabric community forum.I would also take a moment to thank MasonMA, GilbertQ for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
you are using a government license, the issue is likely due to current limitations in the Government Cloud. At this time, PBIP Power BI Project files are not supported in that environment this includes publishing reports or semantic models created in PBIP format.That’s likely why you are seeing the "Publishing failed for an unknown reason" message, and the semantic model shows as disconnected after publishing.
Try this steps you may solve your issue :Convert your PBIP file back to a PBIX file if you have the original or can re-export it.
Reconnect the report to the semantic model in PBIX format.
Then publish both the dataset and the report to the same workspace.
Also, if you are using a gateway or live connection, double-check with your IT team to make sure everything is set up correctly on that end sometimes gateway misconfigurations can also cause publishing or connection issues.
Hope this helps if you have any queries we are happy to assist you further.
Best Regards,
Harshitha.I did try saving both the semantic model and report back as a pbix and I still got the same errors unfortunately.
Hi MaBERG,
Thanks for confirming. Since the same issue happens with PBIX also, it’s likely related to the Government Cloud setup or restrictions in your environment. I think the next step would be to check with your IT/tenant admin so they can review the workspace and connection settings on their side.
Best regards,
Harshitha.
