Problem with Power Platform Pipelines

(0) Share

Report

Posted on by JnanaAgni

Hello,
I did a run of Power Platform Pipelines, but the deployment crashed:

But despite of it crashing, solution was at least partially migrated to the Test Env:

Solution duplicated with _Upgrade added to its name. For 19h now.
I cannot delete it because i get an error, and cannot start another Pipelines deployment, because I get the message that another upgrade is pending.
Do you have any ideas how to solve this?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (14)

Answers (1)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @JnanaAgni

Click on the elipses next to ODK Dataverse solution in Maker portal, and you should get an option to 'Apply upgrade' (or 'Apply Solution Upgrade'). Click that, and hopefully after few mins, the upgrade process will complete. The "ODKDataverse_Upgrade" solution will disappear and "ODKDataverse" solution will be upgraded to new version.

You can also monitor progress within solution history (and also try to troubleshoot the reason for previous failure this way)

Was this reply helpful? Yes No
JnanaAgni 12 on at

Like (0)

Report
Copy link

Link copied!

@parvezghumra When I try to apply upgrade I get an error that dependency is missing (connector to ms translator).
So I cannot apply upgrade, delete the solution or publish another one with dependency included.
Seems like I'm stuck 😉

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report
Copy link

Link copied!

@JnanaAgni Can you paste a screenshot of the actual dependency errors you're referring to please

Was this reply helpful? Yes No
Geeks_D 1,169 on at

Like (0)

Report
Copy link

Link copied!

H @parvezghumra
I am currently faced with this issue and the solution is not applying the upgrade with this error :
Failed to upgrade solution. Solution dependencies exist, cannot uninstall. DependencyCount : 6 RequiredComponentObject details: Type: connectionreference

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report
Copy link

Link copied!

@Geeks_D If you try to apply the upgrade in the classic experience, you'll get a more readable error message and listing of the dependencies. Try that and paste the screenshot of the list of dependencies here

Was this reply helpful? Yes No
Geeks_D 1,169 on at

Like (0)

Report
Copy link

Link copied!

Hi @parvezghumra
This is the using the classic design
System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Sql error: Statement conflicted with a constraint. The DELETE statement conflicted with the REFERENCE constraint "environmentvariabledefinition_environmentvariablevalue". The conflict occurred in database "db_crmcoregbr_20221031_01452565_2076", table "dbo.EnvironmentVariableValueBase", column 'EnvironmentVariableDefinitionId'.
The statement has been terminated. CRM ErrorCode: -2147185375 Sql ErrorCode: -2146232060 Sql Number: 547 (Fault Detail is equal to Exception details:
ErrorCode: 0x80048D21
Message: Sql error: Statement conflicted with a constraint. The DELETE statement conflicted with the REFERENCE constraint "environmentvariabledefinition_environmentvariablevalue". The conflict occurred in database "db_crmcoregbr_20221031_01452565_2076", table "dbo.EnvironmentVariableValueBase", column 'EnvironmentVariableDefinitionId'.
The statement has been terminated. CRM ErrorCode: -2147185375 Sql ErrorCode: -2146232060 Sql Number: 547
TimeStamp: 2024-01-19T10:21:20.3762891Z
--

Was this reply helpful? Yes No
AxelFoley on at

Like (0)

Report
Copy link

Link copied!

I am facing the exact same issue being stuck in not being able to apply the upgrade, cannot delete the existing solutions in destination env nor can I redeploy a modified corrected version. Anybody found a solution yet?

Was this reply helpful? Yes No
Verified answer

Geeks_D 1,169 on at

Like (0)

Report
Copy link

Link copied!

Hi Everyone
So i was able to fix this problem using an Old Artefact from the Deployment Pipeline (Good to have version/Source control)
I imported the solution manually into the Test Environment and changed the version number as well
Then deploy the update with the pipeline and was all good

Was this reply helpful? Yes No
Geeks_D 1,169 on at

Like (1)

Report
Copy link

Link copied!

Do you use the deployment pipeline ?

Was this reply helpful? Yes No
AxelFoley on at

Like (0)

Report
Copy link

Link copied!

Yes, indeed i am using a pipeline. Happens between DEV and STAGE after initial deployment went correctly and I tried to deploy my first delta change (deleting fields from the schema) and trying to redeploy the changes I made in DEV. With this first change to the intial solution, the pipeline breaks.

Was this reply helpful? Yes No