Hi All,
I'm currently on the last step of deploying 365FO on-premise for testing, all left to do is to deploy enviroment from LCS, everyhthing else is already set according to https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/setup-deploy-on-premises-pu12.
The problem is that LCS gives an error every time I try to do it. When checking event viewer on Orch server I found these errors:
"Unable to get deployment artifacts for command <guid>"
"The remote name could not be resolved: 'login.windows.net'"
Sometimes when deplyment fails it gives error:
"Unable to get the channel information"
"The remote name could not be resolved: 'lcsapi.lcs.dynamics.com'"
I could ping lcsapi.lcs.dynamics.com:80 from my Orch server, but couldn't ping login.windows.net:443, "Host is not found" error appears (ports taken from https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/troubleshoot-on-prem).
What I already did:
- disabled Firewall, antivirus, UAC on all servers
- reinstalled local agent
- checked all deployment configurations in LCS, they are correct
- imported all certificates to all servers
- restarted servers
Also, I noticed that agent fileshare directory is left empty when deploying and no files are being downloaded. I already gave Full Acces to 'Everyone' on that fileshare and validated that Credentials.json is correct.
Maybe someone could help me?
Hi Edgar,
We are also facing the same issue.
"Application fabric:/Bootstrapper is not OK after 10 minutes"
How did you solve this ?
Hi Shubham,
You were right at first and problem was in DNS settings, our IT department has fixed it. Thanks.
But now there is other error on Orchestrator server:
"Application fabric:/Bootstrapper is not OK after 10 minutes"
Maybe you know what it can be?
I have heard that timeout like this can happen, because of disk speed, but all of our server have high-speed SSD.
Hi EdgarM ,
it's look like not connecting lcsapi.lcs.dynamics.com
add IP to host file in this path
C:\Windows\System32\drivers\etc\hosts
137.135.14.114(Your IP Address) lcsapi.lcs.dynamics.com
after adding this may be resolve your problem.
Hi Shubham,
Thank you for your reply.
‘.\Test-D365FOConfiguration.ps1’ gives no errors on all servers.
[ping lcsapi.lcs.dynamics.com] didn't manage to connect, but [psping lcsapi.lcs.dynamics.com:80] was successful.
Does it mean that something is blocking it after all?
Hi EdgarM,
Please test below actions on all the orchestrator servers
Run ‘.\Test-D365FOConfiguration.ps1’, it should be no errors.
Check command run [ping lcsapi.lcs.dynamics.com]
If this fails then ask your IT department to review why as something is being blocked by this managed account.
Thanks
Shubham
André Arnaud de Cal...
291,969
Super User 2025 Season 1
Martin Dráb
230,842
Most Valuable Professional
nmaenpaa
101,156