D365FO On-Prem LCS Sandbox environment deployment is stuck with status downloading.

(0) Share

Report

Posted on by Hammam

Hi all,

While using LCS to deploy a user application deployable package on D365FO On Premises, Deployment status is stuck with Downloading for more than 24 hours.

Restart all servers in sequence in the environment did not help.

Checking OrchestratorData database tables OrchestratorJob and RunBookTask do not contain any record related to this deployment.

Agent version is 3.0.0

Application release: 10.0.26 (10.0.1192.76)

Platform release: Update50 (7.0.6354.76)

Any idea how to solve this issue?

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Hana Xue Microsoft Employee on at

Like (1)

Report

Hi,
You can check out old threads similar to your question, where it is mentioned that all servers can be restarted. If restarting does not work, you can restart the AOS node from the Service Fabric cluster, then open LCS and click Refresh Status.
For more details, please check: Solved: LCS on-prem environment update deployment status is always downloading (dynamics.com)
Best Regards,
Hana

Was this reply helpful? Yes No
Hammam 36 on at

Like (0)

Report

Hi Hana,

Thanks a lot for your reply.

Neither restarting all servers through operating system/refresh status nor restarting AOS nodes through Service Fabric/refresh status help in getting out from Downloading status.

Any other idea that may help before trying re-install the local agent or deleting/redeployment of the whole environment?

Was this reply helpful? Yes No
Suggested answer

Komi Siabi 13,093 Most Valuable Professional on at

Like (1)

Report

Hello Hamman,

You do not have to delete the environment and restart. That a whole lot for me , lol.

You can take the LCS back to the most recent successful deployment state by running a script in the OrchestratorData database.

Restore a failed deployment to initial state on LCS : D365FO On-premises

Was this reply helpful? Yes No
Hammam 36 on at

Like (0)

Report

Hello Komi,

Thanks a lot for your reply,

We found no records(JobId nor Runbook TaskId) related to stuck downloading deployment in OrchestratorData database tables OrchestratorJob and RunBookTask.

Last records found are created in 12-April-2023 for a successful package deployment.

Any idea that may help?

Was this reply helpful? Yes No
Suggested answer

Komi Siabi 13,093 Most Valuable Professional on at

Like (0)

Report
You mentioned that the last record in OrchestratorJob table is as of 12-April-2023.
Can you also confirm the same date is what you have for the latest custom package on LCS? : History -> Environment changes.

We found no records(JobId nor Runbook TaskId) related to stuck downloading deployment in OrchestratorData database tables OrchestratorJob and RunBookTask.

No, you are not looking for any information relating to stuck, instead, we want to see the last successful deployment and take the environment back to that clean state. Therefore, run

select * from OrchestratorJob order by LastProcessedDateTime desc select * from RunBookTask order by StartDateTime desc

From RunBookTask table, we are looking for the recent record where name = executePostDeploymentScript.

Please follow the steps once again and revert.

Was this reply helpful? Yes No
Hammam 36 on at

Like (1)

Report

Hi Komi,

Thanks a lot Komi for support,

Confirmed as below,

Was this reply helpful? Yes No
Komi Siabi 13,093 Most Valuable Professional on at

Like (0)

Report

Hi Hammam,

Do you now confirm that the environment is taken back to clean state?

Was this reply helpful? Yes No
Suggested answer

Hammam 36 on at

Like (1)

Report

Hi Komi,

Thanks a lot for your follow-up,

Actually, IT team could not find any solution except for refreshing Local Agents deployment on all nodes using Get-AgentConfiguration.ps1 and Get-DeploymentSettings.ps1

Now system is back to normal state, and we try to re-deploy the required software package,

Thanks to everyone tried to help us,

Best regards,

M.Hammam

Was this reply helpful? Yes No