Timeout loading connection picker during solution import

(1) Share

Report

Posted on by MrPetz

Hi,

During import of a solution to our production environment, a timeout occurs when loading the "connections picker":

Power Apps Connection Timeout.JPG

Any ideas what might be causing this?

I have tried the following:

Import as managed solution
Import as unmanaged solution
Done the same on our development and preprod -> same timeout occurs

I have also tried to import another solution, which is already running on production, on our preprod -> same timeout occurs. The other solution was imported on production a couple of weeks ago without any issues.

BR Morten

Categories:

Error handling

I have the same question (0)

All responses (20)

Answers (1)

TubaGuy 18 on at

Like (0)

Report
Copy link

Link copied!

Did you get a resolution to this?

Was this reply helpful? Yes No
Jal786 9 on at

Like (1)

Report
Copy link

Link copied!

I found that this issue was being caused by a missing dependency from the solution I was trying to import in. I had removed some unnecessary connection refs from my unmanaged solution and packaged to import as managed into uat environment. However the uat solution had some flows with unmanaged layers which were still using and expecting the references I had removed. To fix this I had to one by one open all the flows in uat and environment and delete the unmanaged layer. If you click on 3 dots next to the flow on flow list in solution, you will see option to view layers. Once you have removed all unmanaged layers, retry the import and it will work with no issues. The error you and I got is absolutely meaningless. To get a more meaningful error and error log, open powerapps in classic view and try import. Then when it fails you get option to download error log. Let me know if above works or if any issues

Was this reply helpful? Yes No
TubaGuy 18 on at

Like (1)

Report
Copy link

Link copied!

Thank you so much. We followed the same path and it seems to be working as well.

Was this reply helpful? Yes No
Jal786 9 on at

Like (0)

Report
Copy link

Link copied!

No worries, glad it worked for you too 🙂

Was this reply helpful? Yes No
MrPetz 22 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thank you for the answer!

I have tried to follow your steps, but I think, I have a different issue (with a similar result).

It's a very simple solution only containing the app and a connection to our SQL DB. I have checked for old layers, but there's only an active one, which I can't remove.

In classic mode I'm able to import the solution without any issues, so that step works. However here I run into another issue, when opening the app, where I can't allow connection to the DB:
The only way I have been able to fix that issue previously is by removing the connection and at it again, which I can't do in a managed solution...

The "funny" thing is that I have two very similar solutions (using same DB connection), where I now experience the same issue on import, but back in January I managed to import one of them to our production environment without any issues. I still have the solution zip from back then, and it also fails on import.

So much for using solutions instead of just importing the app...

BR Morten

Was this reply helpful? Yes No
TubaGuy 18 on at

Like (0)

Report
Copy link

Link copied!

I'm not sure how best to guide you on this.

I didn't remove any connections. I removed connection references which cleanup the solution and allowed me to import it.

From your error message it looks like you removed not just the connection reference but the connection. Based on this error I would return to my Unmanaged (Dev) instance and make sure the connection is still part of the solution. Then re-export it and try again.

Sorry I'm not sure what else to recommend.

Was this reply helpful? Yes No
Jal786 9 on at

Like (0)

Report
Copy link

Link copied!

Go back to the environment where the unmanaged solution is. Re-add the connection and export as managed solution back into the Prod environment. You have removed your actual connection from your one active layer. The issues in this thread were referencing scenarios where there was more than one managed layer. Let me know if this works.

Was this reply helpful? Yes No
TubaGuy 18 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your suggestion.

I solved my issue by cleaning up the solution of extra connection refs and reimporting it.

Was this reply helpful? Yes No
Verified answer

MrPetz 22 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

It was a bug in the platform causing the timeout. MS has released a new feature in "import solution" as a bugfix:

BR Morten

Was this reply helpful? Yes No
marcuscrm 2 on at

Like (0)

Report
Copy link

Link copied!

I am having the same issue - how do you enable this feature?

Was this reply helpful? Yes No