I am trying to upgrade a classic workspace to a new workspace, but it fails with an the underlying error being unknown.
This bug does not yet seem resolved as I've tried updating the workspace today and still getting same error as mentioned by @Anonymous
Any additional steps that were taken?
Hi @Anonymous ,
Can you please share more about the error message? You could follow the steps firstly to check if you ignored some details.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Was there a resolution to this question without raising a support ticket? I have followed the steps exactly and have the same issue. Do I just raise a support ticket?
I had the same issue, kept getting unknown error, but found this: https://community.powerbi.com/t5/Issues/Can-t-upgrade-Classical-workspace-to-new-workspace-experienc...
I also removed the logo image (same as person mentioned added and then removed image) and then my upgrade worked, bit of a faff but quicker than raising a support ticket.
Hi @v-xuding-msft ,
I did follow those steps when I got the failure message.
This was the message I received:
Workspace upgrade failed
Please check the technical details for more information. If you contact support, please provide these details.
Underlying Error: UnknownError
Activity ID: 25a4310e-13c2-4a86-91c5-f7d756874426
Correlation ID: 984647e9-2159-9fe1-9c3b-5bc0c7a9b711
Request ID: 6f4a4fd8-5420-f2b6-4fe5-4c7955fd326c
Time: Wed Dec 04 2019 07:42:14 GMT-0600 (Central Standard Time)
Service version: 13.0.11499.187
Client version: 1911.3.022
Cluster URI: https://wabi-us-north-central-redirect.analysis.windows.net/
Thank you. Do you remember the details by chance?
I was speculating that it has something to do that even though I am listed as the workspace admin, perhaps I was not listed as the group owner in the old classic workspaces. I am still trying to troubleshoot this, but wasnt sure if I was on the right path.
I thought the same when I had the issue, but that didn't solve it, unfortunately. No details were given, just that it was a bug that PBI support escalated to the product engineering team.