Finance | Project Operations, Human Resources, ...

DBSync Fails in Production After Service Update - Existing Table Already Exists (SQL 50000)

(3) Share

Report

Posted on by CU16060924-0

Hi everyone,

We're currently facing an issue while deploying a new package to our Dynamics 365 Finance & Operations Production environment, and we're looking for suggestions from anyone who may have experienced something similar.

During the Production deployment, the deployment fails at the DBSync stage with the following error:

SQL 50000: There is already an object named 'RENTALDYNAMICPRICEINVENTORYLEVELTIER' in the database.

The build package is generated successfully, and the same package deploys without any issues in our Development and UAT environments. The table RENTALDYNAMICPRICEINVENTORYLEVELTIER already exists in both UAT and Production, but the deployment fails only in Production.

We have an active Microsoft Support ticket, but the issue is still under investigation, and we're currently blocked from deploying any business-critical changes to Production.

Has anyone encountered this type of DBSync error before?

What was the root cause?

How did you resolve it?

Is there any supported way to recover from this issue in a Microsoft-managed Production environment?

Has anyone seen this happen after a Microsoft Service Update?

We're looking for any suggestions or best practices that could help us move forward while Microsoft continues their investigation.

Any advice or similar experiences would be greatly appreciated.

Thank you!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Subra 1,938 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @CU16060924-0

Could you please let us know which version currently you are using in D365FO?

Additionally, could you please check is there any different between UAT and Prod with the versions?

The above table is a custom table which you have created as part of your customization?

Thanks,
Subra

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 306,659 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi,

In this case, the table is part of a new rental functionality that will be available in the future. At this moment, it is in a private mode. I have seen similar issues before. Microsoft Support should be able to fix this as this is a Microsoft managed table. In case this is "under investigation", raise the severity as not being able to deploy new changes is a kind of production outage. Also try to escalate to the manager.

Potentially, Microsoft can drop the existing Rental table from the production DB. The sync should then be able to recreate it.

Was this reply helpful? Yes No
Suggested answer

Navneeth Nagrajan 2,659 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi @CU16060924-0,
Agree with @André's suggestion.

You need to do either of the following:
1. Drop the table RentalDynamicPriceInventoryLevelTier and then try to do a full build and add the table back and build the package. Would recommend doing a full build of the model where the table resides and then do a reference build with database synchronization. This has to be done in the lower environment and ensure you have a clean build. Based on this, Microsoft support team should be able to perform the steps in the higher environment.
2. In addition to this, check the nuget.config and packges.config version because often it happens that running your build on older versions tends to not pick up newer version errors. nuget.config and packages.config should be a part of the build pipeline process through which the package is being built. Had this problem in the past.

Was this reply helpful? Yes No