The Export and Import Solution task is taking too long and times out after more than 1 hour.

(0) Share

Report

Posted on by vsingh

Hi,

The Export & Import Solution task is taking too long and times out after more than 1 hour.

What i noticed system did not get assembly file and try to resolve assembly more than 1 hour & after 1 hour pipeline task cancle.
For more details attached the log of my pipeline, please look into it.

logs_7425.zip

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Mikkelsen2000 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for sharing the file. We will take a look. In the meantime, can you pls. re-confirm that serverurl, username + password is correct (or TenantID, appID & Secret is using SPN)?

Thanks

Was this reply helpful? Yes No
Verified answer

vsingh 11 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes, already checked everything is correct.
and don't think is authentication related issue.

Was this reply helpful? Yes No
David Jenni Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Looking at your log (thx!), it's apparent that, before it times out due to the 60 min AzDevOps task timeout, your ImportSolution never got to establish a connection (and hence never even initiated the import).
I was able to repro the same timeout (and abort) behavior on a pipeline of mine when using username/password authN for a user that has MFA required. This should cause an error from AAD, but that error unfortunately never made it back to the task, hence the task stalls out.
Your possible work arounds:
- in the AAD tenant for your CDS environment, ensure that MFA is disabled for that user (under Conditional Access)
- or create an appID/ServicePrincipal, add that appID as AzDevOps ServiceConnection and use that to authenticate your import task with

I'll create a fix on our end to ensure the AAD error gets promptly surfaced to the task and push an updated BuildTools extension 1.0.4 or greater

2020-06-19T14:54:00.5539152Z ##[debug]BoundParams: authInfo = System.Collections.Hashtable
2020-06-19T14:54:00.5714118Z ##[debug]authInfo: Credential = System.Management.Automation.PSCredential
2020-06-19T14:54:00.5799291Z ##[debug]authInfo: TenantId =
2020-06-19T14:54:00.5848314Z ##[debug]authInfo: AuthType = OAuth
2020-06-19T14:54:00.5886619Z ##[debug]authInfo: EnvironmentUrl = https://testdevops.crm.dynamics.com/
....
2020-06-19T14:54:00.6214388Z ##[debug]Get-Var: AsyncOperation = True
2020-06-19T14:54:00.6238185Z ##[debug]BoundParams: AsyncOperation = True
2020-06-19T14:54:00.6300410Z ##[debug]Get-Var: MaxAsyncWaitTime = 04:00:00
2020-06-19T14:54:00.6339629Z ##[debug]BoundParams: MaxAsyncWaitTime = 04:00:00
2020-06-19T14:54:00.6391260Z ##[debug]BoundParams: ConvertToManaged = False
2020-06-19T14:54:09.1199956Z VERBOSE: InProcBindingRedirect: 3 - looking to resolve assembly: Microsoft.mshtml, Version=7.0.3300.0, Culture=neutral,
2020-06-19T14:54:09.1205081Z PublicKeyToken=b03f5f7f11d50a3a
>> 60 min no more log until AzDevOps cancels the job due to timeout:
2020-06-19T15:53:05.5963011Z ##[debug]Re-evaluate condition on job cancellation for step: 'Power Platform Import Solution '.

Was this reply helpful? Yes No
vsingh 11 on at

Like
a
(0)

Report
Copy link

Link copied!

To avoid this issue please use service account with no MFA.

Was this reply helpful? Yes No