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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

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

Error in D365 Sales Integration

(4) ShareShare
ReportReport
Posted on by 658
Hello Folks,
 
I am facing the below error while sales integration setup in BC,
The user already has system administrator role,
Please let me know solution of this
 
 
Thanks,
KP
I have the same question (0)
  • Suggested answer
    Sohail Ahmed Profile Picture
    11,169 Super User 2026 Season 1 on at

    Hope this might be helpful:

    The error "The setup failed due to a generic error. Please sign in to the Dataverse organization with an account that has the System Administrator role. Ensure that no other import or deletion of a PowerApps solution is currently in progress. Additionally, verify that the solution file is not broken and that the specified administrator has sufficient privileges," on the D365 Sales Integration Setup page, even when the user has the System Administrator role, points to a specific set of common causes.

    Likely Causes and Solutions:

    Concurrent Dataverse/Power Apps Solution Operations:

     
    • Most Common Cause: The error explicitly mentions "no other import or deletion of a PowerApps solution is currently in progress." This is a frequent blocker.
    • Solution: Ensure absolutely no other solution imports, exports, upgrades, or deletions are running in your target Dataverse (Dynamics 365 Sales) environment. Even a pending or failed operation can cause this. Check the "Solution History" in your Power Platform Admin Center for the environment. Wait for any ongoing processes to complete or resolve any stalled ones.
     
    1. Insufficient Privileges (despite System Admin role):
     
    • While you state the user has System Administrator, sometimes the context of the connection user (the user account used to establish the connection from Business Central to Dataverse) might have an issue.
    • Solution:
    • Re-authenticate: Try to refresh the connection or re-enter the credentials for the Dataverse connection in Business Central. Sometimes, the token might be stale or have issues.
    • Specific Security Role: Verify that the user establishing the connection in Dataverse not only has "System Administrator" but also the "Delegated Admin" role or other specific roles that might be required for solution deployment/configuration in Dataverse. Ensure the user directly has these roles, not just inherited through a team.
     
    1. Broken Solution File (Integration Solution):
     
    • The error mentions "verify that the solution file is not broken." During the initial setup of the D365 Sales Integration, Business Central attempts to deploy a managed solution (the "Business Central Sales Integration" solution) into your Dataverse environment.
    • Solution:
    • Check Dataverse Solutions: Go to your Dataverse environment (Power Apps Maker Portal -> Solutions) and look for a solution named something like "Dynamics 365 Business Central Sales Integration."
    • Clean-up/Re-attempt: If a prior attempt failed badly, there might be a partially deployed or corrupted version. You might need to manually delete any existing "Business Central Sales Integration" solutions from Dataverse (if found and if they are not fully active/functional) before attempting the setup again from Business Central. This should only be done if you are sure it's the specific BC integration solution and not impacting other parts of your Dataverse. Exercise caution here.
     
    1. Network/Firewall Issues:
     
    • Less common for this specific error, but ensure no network or firewall rules are blocking communication between Business Central and the Dataverse URL.

    To troubleshoot effectively:


    • Be patient: Dataverse solution operations can take time.

    • Isolate: Try the setup when no other users or automated processes are touching solutions in your Dataverse environment.

    • Re-attempt: After checking for concurrent operations or manually cleaning up a broken solution, try the setup again from Business Central.

    The most likely culprit is #1 (concurrent solution operations) or potentially #3 (a corrupted previous deployment attempt of the BC integration solution).

     

    ✅ Mark this answer as verified if it helps you.

  • Suggested answer
    YUN ZHU Profile Picture
    99,084 Super User 2026 Season 1 on at
    Hi, hope the following can give you some hints.
    Dynamics 365 Sales and Business Central integration setup (Set up a connection to Dataverse and Set up a connection to Dynamics 365 Sales)
     
    It looks like a problem with this step:
    Thanks.
    ZHU

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

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,005 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,148 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 557 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans