Open Govardhan-gbr opened 4 months ago
Please add the system.debug variable and set it to true.
Then please share the logs
Hi @maikvandergaag , I have added the system.debug variable and set it true. Also attaching the logs in .txt format. Please let me know what action item do i need to perform after. Power BI Publish error for release pipeline.txt
Hi @maikvandergaag any update on the request which I have created please?
No sorry, currently on vacation will be back in one week
Hi Maik, hope you are doing well. Any update on the request please?
Sorry still on vacation but found this in the log:
"error":"invalid_client","error_description":"AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '***'
Issue Description: The release pipeline fails at the Power BI Action: Publish step, despite the build pipeline producing artifacts successfully.
Extension Details:
Extension: Release Task Power BI Actions Version: 5* Steps to Reproduce:
Execute the build pipeline to produce artifacts. Trigger the release pipeline to publish the artifacts to Power BI Workspace. Observe the failure in the Power BI Action: Publish step. Expected Behavior: The release pipeline should successfully publish the artifacts to the Power BI Workspace without errors.
Situation:
Agent Type: Microsoft-hosted agent Authentication: Service principal Extension Version: 5*
Log Information: The error logs are not visible. Please ensure the agent is running in debug mode by setting system.debug to true in the pipeline configuration.
Additional Information: We recently migrated from a classic build pipeline to a 1ES Template pipeline. The build pipeline is functioning correctly, producing the required artifacts. The release pipeline, which relies on these artifacts for publishing to Power BI, is encountering issues. We have verified the configuration for the Power BI Service Connection, which uses a service principal. Screenshots of the configuration and error messages are attached for reference.
We have attempted troubleshooting but are unable to identify the error due to lack of log information. Please assist in resolving this issue, and let me know if further details or actions are required from my end. Attaching the screenshots for reference.