Finance | Project Operations, Human Resources, ...

Unable to trigger servicing operation as the source package

(0) Share

Report

Posted on by brianmaric

Hi, we got this error when trying to deploy a package.

Unable to trigger servicing operation as the source package application version 10.0.995.86 is lesser than the production environment application version 10.0.1084.80

I understand that we need to create a package where the build VM is updated to the most recent version. But where do I find where the Build VM is referenced?

Thanks

I have the same question (0)

All responses (16)

Answers (0)

Suggested answer

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Brian,

You should be able to find the VM being used as a build from Azure DevOps. You can go to the pipeline and click on "Edit" and note the Agent pool used for the pipeline.

You can then go to Project setting and check Agent pools and choose the Agent pool in use. You can then check the agent under the agent pool.

Click on the agent and check the Capabilities. Under system capabilities, you can check Agent.ComputerName. You can find the VM name under Cloud hosted environments .

You have to update this environment to the same version as the Production environment.

Was this reply helpful? Yes No
brianmaric on at

Like (0)

Report

When I click on 'Capabilities' for the specified agent pool, I don't see the System Capabilities. I do see system capabilities for the 'default' agent pool.

Not sure what to make of it.

Was this reply helpful? Yes No
Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Brian,

Not sure if you have permissions for this. You can check if anyone else can see the System capabilities.

If you still can't figure it out, you can check the cloud hosted environments under LCS and check the ones that have Description set to "Build" under Deployment status.

Was this reply helpful? Yes No
brianmaric on at

Like (0)

Report

Ok thanks, does the build VM have to be listed under the agent system capabilities or is there another way to specify the build VM?

Was this reply helpful? Yes No
Gunjan Bhattachayya 35,423 on at

Like (0)

Report

I can't see any other place where it is listed. Were you able to find the VM by any chance?

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi brianmaric,

I think that your problem is related to something else than the build server version.

It's completely OK and supported to build with version X, and deploy to a system that has higher application version.

Instead your issue is caused by the fact that your UAT system has lower D365 version than the prod system. The deployment from UAT to Prod always copies the full application (including MS version and your customizations), and therefore the UAT system must have same or higher D365 version than your prod system. Otherwise you would effectively downgrade your prod system, and this is not possible.

Was this reply helpful? Yes No
brianmaric on at

Like (0)

Report

Yes, but the UAT does have the same version as PROD. Our system was automatically updated to to:

We did update to Prod on Sat and then tried to apply the package built on the lower version on Sunday, but the UAT was already updated.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

As I wrote, the version of the build server doesn't matter, as long as it's same or lower than any system where it will be deployed.

I'm sorry but I don't fully understand this sentence: We did update to Prod on Sat and then tried to apply the package built on the lower version on Sunday, but the UAT was already updated.

Remember that you're not applying packages to Prod anymore, you're promoting the full UAT codebase (assuming you're on Self-service topology which pretty much everyone should be by now).

So if the latest update in UAT and Prod is a Microsoft update, you can't anymore promote some older customization deployment from the UAT to Prod. That snapshot would have a D365 version that is lower than your current Prod version.

Could you please share screenshots that we can understand better?

1) Screenshot of your UAT version (Prod you already shared I believe)

2) Screenshot of what you see in LCS when you try to schedule the PROD update?

Thanks!

Was this reply helpful? Yes No
brianmaric on at

Like (0)

Report

This is the error..

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi,

thanks but could you share more details so that we understand the full process and all the choices that you make.

The error message itself you already shared in the initial message.

So let's start by the Maintain button in the Prod environment LCS page, and then please share screenshot of each step that you take. Thanks!

Was this reply helpful? Yes No