Finance | Project Operations, Human Resources, ...

Unable to schedule deployment for Production

(0) Share

Report

Posted on by Akbarpasha

Hi All,

Getting the below error while scheduling the Production deployment from UAT(Package):

"Unable to trigger servicing operation as the source package application version 10.0.960.43 is lesser than the production environment application version 10.0.995.51."

Please advice us how we can resolve this issue.

Regards,

Akbar

I have the same question (0)

All responses (12)

Answers (0)

Suggested answer

A.Prasanna 8,223 on at

Like (0)

Report

Your Package is built/developed in a DevBox has a lower application version than your Production environment because of version mismatch it won't allow you to deploy, contact your developer.

Was this reply helpful? Yes No
Akbarpasha on at

Like (0)

Report

Hi Amith,

It got deployed in UAT, UAT and PROD is having similar versions but not DEV,

How can we process these changes now?

Do we need to upgrade DEV similar to Prod?

if yes, what will be process , it will be really helpful for me if i get any link for upgrading DEV.

Production:

Version: 10.0.22 (10.0.995.51)

Platform release : PU46 (7.0.6164.49)

UAT:

Version: 10.0.22 (10.0.995.51)

Platform release : PU46 (7.0.6164.49)

DEV:

Version: 10.0.16 (10.0.689.10004)

Platform release : Update40 (7.0.5860.35679)

Regards,

Akbar

Was this reply helpful? Yes No
Alex VN 1,994 on at

Like (0)

Report

Hi,

Can you help to confirm again if the UAT version is the same as Prod on the environment that you are using? Please check both in LCS and application Question Mark - About in the top right corner of the client. The message show that in UAT you might have lower version than Production.

Also may I know if you have another sandbox environment beside the standard UAT?

Regards,

Anh Ong

Was this reply helpful? Yes No
Akbarpasha on at

Like (0)

Report

Hi Ong,

We have only one UAT sandbox.

Version from applications are same in Production and UAT:

Production application version:

UAT application version:

It is similar in LCS as well:

Production:

Application release : 10.0.22

Platform release : PU46 (7.0.6164.49)

My current version : Version: 10.0.22 (10.0.995.51)

UAT:

Application release : 10.0.22

Platform release : PU46 (7.0.6164.49)

My current version : Version: 10.0.22 (10.0.995.51)

But DEV is having different version:

Application release : Microsoft Dynamics 365 for Finance and Operations (10.0.16)

Platform release : Update40 (7.0.5860.35679)

My current version : Version: 10.0.16 (10.0.689.10004)

We were able to deploy package to UAT from DEV, but when deploying to Production from UAT it is throwing that error:

“Unable to trigger servicing operation as the source package application version 10.0.960.43 is lesser than the production environment application version 10.0.995.51.”

Please advise how we can proceed further now.

Regards,

Akbar

Was this reply helpful? Yes No
Alex VN 1,994 on at

Like (0)

Report

Hi,

In this case I would recommend you to open ticket to MS team to check further. For me it seems the version is correct and it can be deployed as per the backward compatibility.

Regards,

Anh Ong

Was this reply helpful? Yes No
Akbarpasha on at

Like (0)

Report

Hi Ong,

Thank you for the inputs,

Just for the confirmation, Production and UAT is having similar versions in Application and in LCS so we can deploy the changes from LCS,

Package is created from Dev which is not similar to Production and UAT.

Package is applied into UAT.

But while applying in Production getting error.

in these case we can raise a ticket with Microsoft? Am I correct.

Please confirm.

Thank you.

Regards,

Akbar

Was this reply helpful? Yes No
Suggested answer

Muthusamy 4 on at

Like (0)

Report

Hi,

Raise a MS ticket and get the Support for this case. Mostly, MS team will request you to update your development environment. However, update here the suggested solutions.

As a best practice, we need to keep all the environments in same versions as like Production & UAT environment.

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/self-service-upgrade

https://docs.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-home-page

Thanks,

Was this reply helpful? Yes No
Akbarpasha on at

Like (0)

Report

Hi All,

Microsoft has suggested us to update the dev environment similar to production.

Is there any step by step process for updating the dev environment as we are doing this first time.It will be really helpful for me.

Thank you.

Was this reply helpful? Yes No
Alex VN 1,994 on at

Like (0)

Report

Hi,

I would recommend you to check for the latest upgrade package that you applied in Production to get the current version and then apply the same package on dev environment normally from LCS to ensure the version is the same.

docs.microsoft.com/.../apply-deployable-package-system

For safety reason, as sometime the upgrade can go wrong so you should backup all your code and DB before doing dev upgrade.

Regards,

Anh Ong

Was this reply helpful? Yes No
Akbarpasha on at

Like (0)

Report
Thank you Anh Ong,

I have gone through the provided link, steps are like:

For a binary update, upload the package directly to the Asset library. For information about how to download an update from LCS, see Download updates from Lifecycle Services (LCS). For an application (AOT) deployable package that results from an X++ hotfix, or from application customizations and extensions, create the deployable package in your development or build environment, and then upload it to the Asset library.

Open the Environment details view for the environment where you want to apply the update.

Click Maintain > Apply updates to apply an update.

Select the package to apply. Use the filter at the top to find your package.

Click Apply. Notice that the status in the upper-right corner of the Environment details view changes from Queued to In Progress, and an Environment updates section now shows the progress of the package. You can refresh the page to check the status.

Continue to refresh the page to see the status updates for the package application request. When the package has been applied, the environment status changes to Deployed, and the servicing status changes to Completed.

in our case Service Update - 10.0.22, is already there in Asset library, so we can directly apply updates from it, am i correct.

Before that i will take our code backups and DB backup.

Was this reply helpful? Yes No