Finance | Project Operations, Human Resources, ...

On-prem sandbox is in deploying state on LCS

(0) Share

Report

Posted on by Community Member

On-prem sandbox environment is in deploying state on LCS for past 15hrs. Not sure know how to stop it.

Service fabric shows all applications and nodes are up.
Tried restarting all aos & orchestrator nodes via service fabric.
Orchestrators & aos nodes showing no errors in event viewer
FO application is accessible via url but not authenticating any user.

What should I do?

Many thanks in advance.

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

A.Prasanna 8,223 on at

Like (0)

Report

there is a similar issue, in the below thread.
https://community.dynamics.com/365/financeandoperations/f/dynamics-365-for-finance-and-operations-forum/296962/lcs-on-prem-environment-update-deployment-status-is-always-downloading
Try to follow the same. Hopefully, it will fix your issue.

Was this reply helpful? Yes No
Suggested answer

Leo Chen on at

Like (0)

Report

1. Try options in the reference thread including - refresh state button on LCS, restart all orcheastrator physical servers one after another. validate the local agent connection on LCS > Project settings> on-prem connector. Resolve any issue if you encounter. You might have to reinstall local agent.

2. It's strange none of AD users is authenticated. Run select * from userinfo where id = 'admin' in backend SQL server management studio to see what is the correct email address for the admin user, and if it's disabled by accident. Probably you might want to rerun the SQL server setup step in the installation guidance article, to reinitiate the admin user.

3. Last option would be to redeploy D365FFO on-prem, once you validate above 2.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Hey Leo,

Thank you so very much for your suggestion.

We fixed it by doing the following steps:

Run the following SQL command to check the last successful update:

select top 1 * from OrchestratorJob order by LastProcessedDateTime desc;

select top 1 * from RunBookTask order by StartDateTime desc;

Then update their State field from 2 to 1 in both queries like this.

update OrchestratorJob set State = 1 where JobId = 'your_job_id';

update RunBookTask set State = 1, Retries = 1 where RunbookTaskId = 'runbook_task_id';

Now the LCS is showing download retry button, so retry it and update environment.

Once this update is done, we re-updated the environment with the new package uploaded in the assets.

Was this reply helpful? Yes No