Finance | Project Operations, Human Resources, ...

Unable to deploy packages in Azure pipeline after 10.0.34 upgrade

(0) Share

Report

Posted on by LEOCGF

I am in the process of upgrading our D365FO sandboxes to 10.0.34.

All the upgrades in cluding our Tier 1 sandboxes were successful.

How ever we had to upgrade an 3rd party ISV layer, so our team installed the package succesfully in Tier1 server, merged the code successfully to our Main Branch in Devops, then we ran our Azure Pipeline succesfully, but when we released to our first Tier2 sandboxes it errored out during the /Deploy to Environment/ phase with the generic error / Asset not successfully deployed. / then it rolled it back.. No other errors were logged than that,.

Would be a versioning issues inside the Azure Pipeline ? Any suggestions would be appreciated.

I have the same question (0)

All responses (4)

Answers (0)

André Arnaud de Cal... 303,446 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Leocgf,

Have you downloaded the deployment logs and checked all details where and why it failed? Can you try to deploy the same package to another Tier-1 environment?

Did the ISV solution provide a deployable package, models or both? Do you have customizations on top of the ISV solution?

Was this reply helpful? Yes No
LEOCGF 25 on at

Like (0)

Report
Copy link

Link copied!

Deployment logs reveal very little other than failure - no reason or code for failure

2023-06-27T23:13:08.5873081Z Start deployment V2
2023-06-27T23:13:24.1802336Z Successfully started deployment of asset 'xxxxxxxxxxxxxxxxxxxxxx to environment 'xxxxxxxxxxxxxxxxxxxxxxxx with activity id 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
2023-06-27T23:13:24.1810608Z Waiting for deployment to complete...
2023-06-27T23:18:24.5426682Z Status: InProgress
2023-06-27T23:23:25.7439266Z Status: InProgress
2023-06-27T23:28:26.1293837Z Status: InProgress
2023-06-27T23:33:26.6688719Z Status: InProgress
2023-06-27T23:38:27.0211446Z Status: InProgress
2023-06-27T23:43:27.4636583Z Status: RollbackInProgress
2023-06-27T23:43:27.6425498Z ##[error]Asset not successfully deployed.
2023-06-27T23:43:27.6873928Z ##[section]Finishing: Deploy to environment fxxxxxxxxxxxxxxxxxxxxxxxxxx

The single deployable package works in our CHE Tier 1 Environments.

We have our support vendor set the deployable package up as the do have a couple of their own customizations that enhance the out of the box feature of the ISV product.

Replying to:

Andre Arnaud de Calavon on 28 Jun 2023 at 14:10:56

Like(0)

Report

Unable to deploy packages in Azure pipeline after 10.0.34 upgrade

Hi Leocgf,

Have you downloaded the deployment logs and checked all details where and why it failed? Can you try to deploy the same package to another Tier-1 environment?

Did the ISV solution provide a deployable package, models or both? Do you have customizations on top of the ISV solution?

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 303,446 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

From the environment history, you can download a zip file with the logs. Doesn't that zip file contains a file ending with Error.log?

Anyway, if the package can be installed on a Tier-1 environment and not on Tier-2+, check if there are ISV or customization models having any reference to a model ending with the part formadapter. Form adapter models are available on a Tier-1 environment (for testing and validation purposes) but not on Tier-2+ (UAT, production) environments. If there is a model having a reference to such form adapter model, the deployment will fail. It can be also any other model reference for which model is not available on your UAT environment. Or maybe a data model change got implemented, but the DB synchronization failed.

Was this reply helpful? Yes No
LEOCGF 25 on at

Like (0)

Report
Copy link

Link copied!

above is the full list of files in the downloaded error log in Azure Pipeline with the failure. The "error" snippet I attached in previous response if from file #4. As stated, frustratingly vague.

I have reviewed your response Andre, much appreciated, and will forward to your comments to the. I haven't heard back from Microsoft support on my submitted case., hope to today. I've been bugging the ISV vendor, they've provided a few "try this" ideas to implement...hopefully we hit a solution soon.

<end reply>

replying to:

Andre Arnaud de Calavon on 28 Jun 2023 at 22:13:37

Like(0)

Report

Unable to deploy packages in Azure pipeline after 10.0.34 upgrade

From the environment history, you can download a zip file with the logs. Doesn't that zip file contains a file ending with Error.log?

Anyway, if the package can be installed on a Tier-1 environment and not on Tier-2+, check if there are ISV or customization models having any reference to a model ending with the part formadapter. Form adapter models are available on a Tier-1 environment (for testing and validation purposes) but not on Tier-2+ (UAT, production) environments. If there is a model having a reference to such form adapter model, the deployment will fail. It can be also any other model reference for which model is not available on your UAT environment. Or maybe a data model change got implemented, but the DB synchronization failed.

Was this reply helpful? Yes No