Home

azure-quickstart-templates for sql server 2016 cluster

%3CLINGO-SUB%20id%3D%22lingo-sub-182154%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-182154%22%20slang%3D%22en-US%22%3E%3CP%3EI%20configured%20regular%20SQL%20clustering%20not%20SQL%20cluster%20%26amp%3B%20always%20on%20because%20we%20were%26nbsp%3B%20using%20SQL%20standard%20edition%20which%20was%20not%20support%20SQL%20always%20on%20cluster%2C%20for%20more%20information%20please%20look%20this%20link.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblog.pythian.com%2Fbuilding-sql-server-failover-cluster-instances-cloud-windows-server-2016-storage-spaces-direct%2F%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fblog.pythian.com%2Fbuilding-sql-server-failover-cluster-instances-cloud-windows-server-2016-storage-spaces-direct%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181928%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181928%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20coming%20back.%20So%20did%20you%20end%20up%20creating%20the%20always%20on%20cluster%20manually%20without%20using%20the%20ARM%20template%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181854%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181854%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20not%20get%20it%2C%20i%20configured%20my%20own%20SQL%20cluster%20by%20using%20Storage%20space%20(S2D).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181839%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181839%22%20slang%3D%22en-US%22%3EMy%20comment%20answer%20to%20your%20question%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-181648%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-181648%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20receiving%20this%20same%20error%20as%20well.%26nbsp%3B%20Has%20anyone%20resolved%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179093%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179093%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20have%20exactly%20the%20same%20issue%2C%20have%20you%20got%20it%20sorted%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3CP%3EJan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-146083%22%20slang%3D%22en-US%22%3Eazure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146083%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20was%20try%20to%20install%20this%20microsoft%20template%20(%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMSBrett%2Fazure-quickstart-templates%2Ftree%2Fmaster%2Fsql-server-2016-fci-existing-vnet-and-ad%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fgithub.com%2FMSBrett%2Fazure-quickstart-templates%2Ftree%2Fmaster%2Fsql-server-2016-fci-existing-vnet-and-ad%3C%2FA%3E).%20i'm%20using%20Azure%20AD%20domain%20services%20the%20users%20i'm%20using%20are%20member%20of%20(AAD%20DC%20Administrators)%20for%20installation.%20while%20deploying%20i'm%20getting%20the%20following%20errors.%20any%20support%20highly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3EOPERATION%20ID%2056DD0C954C942078%20TRACKING%20ID%20db38a95d-a600-4d58-a982-3054b152ccab%20STATUS%20Conflict%20PROVISIONING%20STATE%20Failed%20TIMESTAMP%201%2F17%2F2018%2C%202%3A11%3A04%20PM%20DURATION%2018%20minutes%203%20seconds%20TYPE%20Microsoft.Compute%2FvirtualMachines%2Fextensions%20RESOURCE%20ID%20%2Fsubscriptions%2F96d29ba6-0c18-4d27-9d75-01b68e33f0f2%2FresourceGroups%2FRCT_RCI_PROD%2Fproviders%2FMicrosoft.Compute%2FvirtualMachines%2Frctdbcls-fci-1%2Fextensions%2FsfciPrep%20STATUSMESSAGE%20%7B%20%22status%22%3A%20%22Failed%22%2C%20%22error%22%3A%20%7B%20%22code%22%3A%20%22ResourceDeploymentFailure%22%2C%20%22message%22%3A%20%22The%20resource%20operation%20completed%20with%20terminal%20provisioning%20state%20'Failed'.%22%2C%20%22details%22%3A%20%5B%20%7B%20%22code%22%3A%20%22VMExtensionProvisioningError%22%2C%20%22message%22%3A%20%22VM%20has%20reported%20a%20failure%20when%20processing%20extension%20'sfciPrep'.%20Error%20message%3A%20%5C%22DSC%20Configuration%20'PrepSFCI'%20completed%20with%20error(s).%20Following%20are%20the%20first%20few%3A%20PowerShell%20DSC%20resource%20MSFT_xWaitForADDomain%20failed%20to%20execute%20Set-TargetResource%20functionality%20with%20error%20message%3A%20Domain%20'riskcontroltech.com'%20NOT%20found%20after%2020%20attempts.%20The%20SendConfigurationApply%20function%20did%20not%20succeed.%5C%22.%22%20%7D%20%5D%20%7D%20%7D%20RESOURCE%20rctdbcls-fci-1%2FsfciPrep%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-146083%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAutomation%20and%20DSC%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esql%20cluster%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893023%22%20slang%3D%22en-US%22%3ERe%3A%20azure-quickstart-templates%20for%20sql%20server%202016%20cluster%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893023%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20this%20is%20an%20old%20thread.%20However%2C%20for%20others%20running%20in%20to%20the%20domain%20not%20found%20issue%3A%20Ensure%20the%20admin%20username%20and%20password%20referenced%20as%20a%20parameter%20in%20the%20template%20is%20a%20%3CSTRONG%3Edomain%20admin%3C%2FSTRONG%3E%20on%20the%20domain%20you%20are%20creating%20the%20cluster%20resources%20in.%20This%20isn't%20intended%20to%20be%20a%20local%20admin%20on%20the%20SQL%20VMs%20but%20a%20domain%20account%20with%20domain%20admin%20permissions.%20Also%20ensure%20you%20can%20ping%2Fnslookup%20the%20FQDN%20to%20the%20domain%20to%20rule%20out%20a%20network%20level%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Shalaw Qader
New Contributor

Hi,

 

i was try to install this microsoft template (https://github.com/MSBrett/azure-quickstart-templates/tree/master/sql-server-2016-fci-existing-vnet-...). i'm using Azure AD domain services the users i'm using are member of (AAD DC Administrators) for installation. while deploying i'm getting the following errors. any support highly appreciated.

 

  • 56DD0C954C942078
  • db38a95d-a600-4d58-a982-3054b152ccab
  • Conflict
  • Failed
  • 1/17/2018, 2:11:04 PM
  • 18 minutes 3 seconds
  • Microsoft.Compute/virtualMachines/extensions
  • /subscriptions/96d29ba6-0c18-4d27-9d75-01b68e33f0f2/resourceGroups/RCT_RCI_PROD/providers/Microsoft.Compute/virtualMachines/rctdbcls-fci-1/extensions/sfciPrep
  • { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMExtensionProvisioningError", "message": "VM has reported a failure when processing extension 'sfciPrep'. Error message: \"DSC Configuration 'PrepSFCI' completed with error(s). Following are the first few: PowerShell DSC resource MSFT_xWaitForADDomain failed to execute Set-TargetResource functionality with error message: Domain 'riskcontroltech.com' NOT found after 20 attempts. The SendConfigurationApply function did not succeed.\"." } ] } }
  • rctdbcls-fci-1/sfciPrep
7 Replies

Hi,

I have exactly the same issue, have you got it sorted?

 

Cheers

Jan

I am receiving this same error as well.  Has anyone resolved? 

My comment answer to your question

I did not get it, i configured my own SQL cluster by using Storage space (S2D).

Thanks for coming back. So did you end up creating the always on cluster manually without using the ARM template?

Highlighted

I configured regular SQL clustering not SQL cluster & always on because we were  using SQL standard edition which was not support SQL always on cluster, for more information please look this link.

https://blog.pythian.com/building-sql-server-failover-cluster-instances-cloud-windows-server-2016-st...

 

I know this is an old thread. However, for others running in to the domain not found issue: Ensure the admin username and password referenced as a parameter in the template is a domain admin on the domain you are creating the cluster resources in. This isn't intended to be a local admin on the SQL VMs but a domain account with domain admin permissions. Also ensure you can ping/nslookup the FQDN to the domain to rule out a network level issue.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
30 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies