Yvand
commented
1 year ago Sorry for the delay and thank you for reporting this. This issue happens randomly but it is very rare, and I found no obvious cause. Did it happen just 1 time or were you able to reproduce it multiple times?
SharePoint Subscription / 2019 / 2016 / 2013 all configured https://github.com/Azure/azure-quickstart-templates/tree/master/application-workloads/sharepoint/sharepoint-adfs
Issue Details
Operation ID: /subscriptions/01e81711-2d2e-4576-8d30-ba62773c438d/resourceGroups/cloud-shell-storage-westus/providers/Microsoft.Resources/deployments/Microsoft.Template-20220929172611/operations/87559CE45372A5DB
Operation name: 87559CE45372A5DB
Provisioning operation: Create
Status: Conflict
Type: Microsoft.Compute/virtualMachines/extensions
Status message:
{ "status": "Failed", "error": { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'ConfigureSQLVM'. Error message: \"DSC Configuration 'ConfigureSQLVM' completed with error(s). Following are the first few: Exception calling \"FindOne\" with \"1\" argument(s): \"The directory service is unavailable.\r\n\r\nName: \"webmethod.local\"\r\n\" PowerShell DSC resource MSFT_WaitForADDomain failed to execute Set-TargetResource functionality with error message: No domain controller was found. (WFADD0010) The SendConfigurationApply function did not succeed.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot " } }
Resource ID: /subscriptions/01e81711-2d2e-4576-8d30-ba62773c438d/resourceGroups/cloud-shell-storage-westus/providers/Microsoft.Compute/virtualMachines/SQL/extensions/ConfigureSQLVM
Resource: SQL/ConfigureSQLVM
Deployment correlation ID: 2b9ba805-acc1-4dc7-96af-968557ea9ed9
clicked the create azure button, and I had to make one adjustment to allow an increased number of CPU's for my west region; outside of that, I didn't do anything other than filling out the form and I added 120GB HD to the SharePoint servers (which are set to ))
The DC had not completed before the SQL server returned that message, the DC finished a couple of min later and had no issue. (at least none returned by azure)