Service update deployment of Dynamics 365 Finance V10.0.39 fails

(1) Share

Report

Posted on by Celeste

293

Service update deployment of Dynamics 365 Finance V10.0.39 fails
We are trying to deploy the Service update V10.0.39 to a Sandbox environment. It initially failed due to license algorithm changes that was required by an ISV. Code changes was deployed successfully to the environment, but the update is still failing.

The service update package that we’re deploying, was saved from the Available updates section under the sandbox environment in LCS, and uploaded to Asset Library. The build version is build 10.0.1860.68

Downloading the error logs, the following SqlException is thrown:
There is already an object named 'LICENSING_POPULATEROLEPRIVILEGELICENSEMAPV2' in the database.

Any assistance will be appreciated greatly.

I have the same question (0)

All responses (5)

Answers (1)

Judy Microsoft Employee on at

Like (1)

Report

Hi, for the error messages, maybe you can try to delete the existing object 'LICENSING_POPULATEROLEPRIVILEGELICENSEMAPV2' from the database after you have backed it up.
Then you can retry the service update deployment to see if it can help.

Hope other experts can suggest on this.

Best Regards,

Judy

Was this reply helpful? Yes No
Anthony Blake 2,926 Super User 2025 Season 2 on at

Like (0)

Report

Looks suspiciously related to your ISV License issue, did you reraise with the ISV.

Related to this: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/removed-deprecated-features-platform-updates#feature-deprecation-effective-february-2024

Was this reply helpful? Yes No
Verified answer

Celeste 293 on at

Like (1)

Report
The issue has been resolved, there were two things that we needed to do:

1: ISV license issue:

Confirm with all ISVs if latest versions should be deployed (if the ISV is used the SHA1 algorithm for generating licenses).
In our case, I redeployed Dynaway modules as well as license.
Create a new deployable package with the re-deployment and deploy to the environment before attempting the upgrade.

2: If the upgrade fails with an issue with procedure [DBO].[LICENSING_POPULATEROLEPRIVILEGELICENSEMAPV2], perform these steps:

Create a Just in Time session on the environment and login to the Microsoft SQL database

Expand the AxDB under Databases

Under stored procedures, right click on object [DBO].[LICENSING_POPULATEROLEPRIVILEGELICENSEMAPV2]

Script to new query window and save query (to have a backup)

Click on Create new query and select database AxDB

Run this script:

DROP PROCEDURE IF EXISTS LICENSING_POPULATEROLEPRIVILEGELICENSEMAPV2

GO

Exit Microsoft SQL

Then Upgrade environment.

Was this reply helpful? Yes No
Nick Jordy 9 on at

Like (0)

Report

How would you do the Drop Procedure on a tier 3 Production environment (cloud deployment)? Would that need to be handled by Microsoft?

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (0)

Report

@Nick,

In case there are issues with an update deployment on a production environment, you would need to create a ticket for Microsoft Support. Microsoft is indeed handling this type of issue as there is no direct access to the service.

Was this reply helpful? Yes No