web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Error Extension when Copy Environment from production

(0) ShareShare
ReportReport
Posted on by 10

Hi,

I'm using the Business Central SaaS, I have an error in the production.

So I need to copy the Production Environment to the Sandbox Environment.

When I copy the Production, I got this error:


Error

 
Environment creation failed. The following extension(s) copied to the new environment are already published as development extensions in an existing sandbox environment on another tenant.
.....

I know I got this error because in the Production Environment, I have an extension from appsource (registered extension).
How to copy the environment without this error? 
I have the same question (0)
  • Suggested answer
    Jyotsna NAV Profile Picture
    on at

    Hello,

    Please check your AppId. Maybe it is the same as another extension, change the AppId and try again.

    Regards

    Jyotsna

    jyotsnanav.blogspot.com

    Please mark this answer as verified if it answers your question. Thank you.

    Don't forget to help the community by verifying the answer or at least like the suggestion if it did help in any way. It will let others know that the topic has verified answer and was beneficial to you.

  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at

    If, when creating a new sandbox environment as a copy of a production environment, you receive a message indicating that the environment creation failed due to an existing development extension, it is related to violation of uniqueness requirements for extension packages.

    Typically this situation is the result of the production environment being copied having an extension package installed with the same app ID, name, publisher, and version as a development extension published to another sandbox environment within the same application service. To resolve this situation, remove the development extension by unpublishing it via the Extension Management page of the other sandbox environment once you have made sure you have a backup of the extension development files. After this is completed you can attempt to copy a production environment to a sandbox again. It is recommended that when you create the extension package for distribution, you use a different app ID than that used for your development extension, which will help you avoid this conflict between your development sandbox and your customer’s production and sandbox environments.

  • Rio Arifin Profile Picture
    10 on at

    Thanks for your reply Jyotsna and Stefano,

    I always build extensions with different AppID

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

[Smoke test 2510.1]

Quick Links

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans