Hello, I am trying to publish an app and am coming across this message:
Activity ID: af88ba02-93f0-4d30-b5e7-a4ed17fbb1ceRequest ID: e4ac52df-05a0-e890-a644-7e04c5c775b3Correlation ID: b5f32895-f62c-bd43-bafd-d681684092ceTime: Mon Aug 01 2022 11:23:05 GMT+1000 (Australian Eastern Standard Time)Service version: 13.0.18756.45Client version: 2207.4.12439-trainCluster URI: https://wabi-us-east2-redirect.analysis.windows.net/
It doesnt exactly tell me what the problem is. Could someone please assist?
There is the same issue here and you can find the expected fix date about it and potential workaround:
Best Regards,Community Support Team _ Yingjie Li
Hi I have the same issue and it is a big problem.
Below the data of the message:
Activity ID: a4e86965-a028-446f-b0d9-c87196d5fdd7Request ID: c427fd42-8ff3-9ab7-4e5c-7b0887d3e4b9Correlation ID: 5666805a-e226-d569-8fc7-fb5223abda99Time: Mon Aug 01 2022 08:30:50 GMT+0200 (Central European Summer Time)Service version: 13.0.18756.45Client version: 2207.4.12439-trainCluster URI: https://wabi-west-europe-redirect.analysis.windows.net/
I am doing some tests:
I tried to create a new workspace and using the pipeline feature I copied al reports and datasets in the new workspace. The same, I am not able to publish the new apllication.
I am thinking that the problem is caused by the pipeline, beacuse DEV enviroment (where I publish the files directly by PBI desktop ) is working fine, while Test and Production (deploy using the pipeline) not.
@v0v0 are you using the pipeline to publish the reports?
@andrewbiolotb I am trying to publish 8 reports to the app. 7 of the reports work, but 1 fails. It fails both in the pipeline and both when I try to update the app.
Activity ID: 1ff0e8d4-3476-4179-8693-9bf976635932Request ID: bcadab47-7115-18fb-8a0a-9ec159cd3f20Correlation ID: 7ecf6527-93cf-0af6-3c8e-06e0674ec4adTime: Mon Aug 01 2022 12:18:31 GMT-0500 (Central Daylight Time)Service version: 13.0.18756.45Client version: 2207.4.12439-trainCluster URI: https://wabi-north-europe-o-primary-redirect.analysis.windows.net/
@v-yingjl many thanks.
The workaround is working for me. Waiting for the final fix
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.