Share
ReportHi 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!
All responses (
Answers (
1,770
