500 error when publishing report to preview v2 workspace and other errors

[alexdupler]

1) When republishing an existing report to our v2 workspace we get a 500 error and are unable to publish. deleting the report and associated dataset from the workspace unblocked us and we were able to publish.

2) Now that we've published an app from the workspace, we are unable to publish new reports to the workspace. Unpublishing the app and then republishing the app is not an option as the app is already distributed to 100 people.

3) when going to the schedule refresh page of a dataset someone else published, in the preview workspace, the "Take Over" button give an error as well.

[JSummersgill]

@v-qiuyu-msft - is there a work around available for the report publish issue? We are currently unable to publish any of our reports from Desktop without getting the "(500) Internal Server Error" as workspaces all have published apps which we do not want to unpublish.

[alexdupler]

Thanks for follwoing the ball on this all the way, Qiuyun,

-Alex

[runtim]

There is a work around to publishing from the desktop.  You can upload the pbix file directly to the service. Make sure you have the workspace opened, then go to Get Data, Create New Content, and select files.

[janatap]

@runtim Nice, it works! I wish I knew that last week... 🙂

[JSummersgill]

Any update on when this is likely to be fixed? The workaround of uploading the file into the service works, but it would be much nicer to have the actual functionality to be able to publish directly from within PBI Desktop.

[v-qiuyu-msft]

Hi all, 

Both report publish and dataset take over issue are fixed on MSIT. Currently the issue still occurs in PROD, I have sent a email to consult this issue internally, will back and update once I get information. 

Best Regards,
Qiuyun Yu 

[dslatteryHCA]

Any update on this issue? I have reports and datasets that are deployed and in production and need to re-publish changes to the dataset.

[janatap]

My issue (publishing) was fixed two days ago... now everything seems to be working correctly.

[JSummersgill]

I'm still getting the same issue this morning:

[Anonymous]

I have the same issue aswell.