-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/uplift-vagrant/crm-dev vagrant sometimes fails #5
Comments
This is the error in the log:
|
A workaround is to re-run:
|
I connected via RDP and run this in PowerShell:
it returned an object so no issue here. |
Found a support article but diagnostics is positive, no issues:
|
Right, from what we see, it might be that groups or other AD objects aren't ready yet? CRM provision consists of several steps, one of which setups a minimal set of AD users and groups. At least two ideas here:
We actually do this for DC provision. Some of the win services take time to get up, so we try/catch until they come online and only then report a successful DC setup. Bypassing this results in failing user/group resolution against AD. Could be same case here.
All modules are pinned, we pin versions to avoid configuration drifts. As you can see, current output does not provide CRM intall progress:
We need to update Dynamics365Configuration version here: You already merged Dynamics365Configuration PR with this feature, right? That way we would see real-time output. Logs won't get lost during first Vagrant provision. So for the group, after DSC group setup, we might do it several times, try to lookup the group until it's there. One more option - is there any way to run CRM pre-install validation before actually install? |
vagrant output: https://gist.github.com/shurick81/392d1ef6330cb0762a041b99581d865e
dynamics installation log: https://gist.github.com/shurick81/b618fbbe2bcdb1293df50688a8b05b1e
The text was updated successfully, but these errors were encountered: