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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / [Microsoft.PowerApps.A...
Power Apps
Answered

[Microsoft.PowerApps.Administration.PowerShell][New-AdminPowerAppEnvironment] Wait that all out of the box solutions imported before responding to caller

(0) ShareShare
ReportReport
Posted on by 33

Hello everyone,

Working on some automation around environment provisioning and solution import on the brand-new environment, I found that when you got an answer from your call to New-AdminPowerAppEnvironment there are still some "out of the box" solutions importing in background.

Below you will find the error message I get in my scenario when I try to import the solution:

 

Error: Cannot start the requested operation [Import] because there is another [LanguageProvision] running at this moment. Use Solution History for more details. -- The solution installation or removal failed due to the installation or removal of another solution at the same time. Please try again later.

 

Do you think it could be possible to wait the import of all the out of the box solutions before sending the response to a call to New-AdminPowerAppEnvironment?

You can find some resources regarding this issue below:

Thank you in advance for your help!

Raphael

  • Verified answer
    Kevin Tempels Profile Picture
    34 on at

    Hi,

    After looking into New-AdminPowerAppEnvironment I noticed there is a -WaitUntilFinished flag.
    I haven't been able to test this out if this works.
    But looking at the GitHub code you sent, I don't see you using this flag.2020-12-07 20_33_28-Window.png

    I'm wondering if this solves it.

  • Rapothin Profile Picture
    33 on at

    Hi,

     

    Good idea!

    I thought I tried all the combinations of parameters of the New-AdminPowerAppEnvironment cmdlet, but it seems it was not the case.


    I have made some tests and indeed, add "-WaitUntilFinished 1" in the call to the cmdlet seems to work.

    I will try to make more tests in the incoming days to be sure that the solution works.

     

    Thank you again for your help.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 342 Super User 2026 Season 2

#2
M Bilal Khan Profile Picture

M Bilal Khan 258

#3
Mohsin Ali Profile Picture

Mohsin Ali 231

Last 30 days Overall leaderboard