D365 FnO Environment deployment fails after 60 minute timeout

(1) Share

Report

Posted on by Mandeep.S

217

Hello community,

I have been trying to deploy an on-prem sandbox via lcs unsuccessfully for the past few days.

The StandaloneSetup.zip download keeps timing out after 60 mins. The size is usually 2.65 GB, but it downloads only 1.4~1.5 GB in the 60 min time limit and fails.

When I psping lcsapi.lcs.dynamics.com:443, I get a 230 ms latency on average, so I thought maybe there is an issue with my network or ISP... in the last 3 days I have tried 3 different ISPs and 2 separate geographic locations in India but the psping doesn't get better than 230 ms. The psping results for google.com or other common sites are within 30 ms.

Is there a way to change the 60 min timeout?

Has anyone had a similar issue? How did you resolve it?

Any ideas at this point would be helpful.

Thanks.

All responses (4)

Answers (1)

Mandeep.S 217 on at

Like (1)

Report

D365 FnO Environment deployment fails after 60 minute timeout

Thanks Komi Siabi,

That suggestion worked. Appreciate the support.

Cheers.
Verified answer

Komi Siabi 12,711 Most Valuable Professional on at

Like (1)

Report

D365 FnO Environment deployment fails after 60 minute timeout

Yes, please.
Re-install local agent.
Mandeep.S 217 on at

Like (0)

Report

D365 FnO Environment deployment fails after 60 minute timeout

Thanks for your suggestion Komi Siabi.

I tried this by changing the localagent-config.json - the result was the same, the deployment timed out after 60 mins, downloaded half of the package.

Should I redeploy the Local Agent on the Orchestrator, because the localagent-config.json file is changed, then delete the LCS environment and create a new one?
Suggested answer

Komi Siabi 12,711 Most Valuable Professional on at

Like (1)

Report

D365 FnO Environment deployment fails after 60 minute timeout

This could be that the download speed between your VM and LCS is slow. You can test the speed, by simply trying to download the agent installer.

Also, increase the timeout to 240 from 60.

Also update the following values:

initialDownloadBlockSizeMB to 4

downloadBlockSizeMB to 5

networkTimeoutInMinutes to 240.

You can make all these changes in the localagent-config.json file.

LCS should be able to download the application package.

By the way I moving the question to the Finance forum. (From Dynamics 365 General)