SQL Cluster: There was a failure to call cluster code from a provider


You have had successfully configured SQL Server 2016 (or other version) cluster on the first node and tried to add the second node to the cluster, but with no luck:

“Microsoft.SqlServer.Configuration.Cluster.EnumerateClusterSupportedIPAddressResourcesAction” threw an exception during execution.Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The cluster group could not be determined for resource ‘Cluster IP Address’. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4098. Description: Not found

  • Both servers running on Windows Server 2016
  • SAN and MPIO are configured
  • Cluster is up and running
  • Migration of cluster resources works fine
  • There are no network issues between the servers
  • You use appropriate user account for setting the cluster

Solution 1: 

If you don’t have Internet on servers and can’t update them, start SQL Server installation on the node with the lower build number. For example, my SQL01 node had 14393.2273 build, while SQL02 – 14393.447. So, I used SQL02 as a first cluster node, and then added SQL01 to the cluster.  In my case, such configuration was just for test/demo, so I can’t recommend that solution for production even if the cluster seems to work fine.

Solution 2:

Just update your servers and make sure that they all have the same build number. Then, run cluster validation report, it should be “green”. Re-run cluster setup wizard on the second node.

Building Windows images with Packer

Hi, folks!

Sometimes you need to create a base or custom image to use one in any kind of automated deployments (CD pipelines, Dev, QA  and etc.) in cloud or on-premises environments. Then, you might start searching for a good solution to make your task easier. Built-in sysprep?  Well, it’s a classic way for Windows without any additional functionality that might be required especially for clouds. So, what can be used for such task?  Definitely, Packer from HashiCorp would be one of the best tool. It allows you to build your custom image from Marketplace image (as for example) and place that image to the Azure Images for further usage.

In the JSON-example below, Packer uses provided options for authentication (variable section) and passes them to the Azure Resource Manager builder section. Packer supports a bunch of builders such as Azure, Hyper-V, VMware or AWS . In my case, Packer uses Azure RM and it’s Windows Server 2019-Datacenter marketplace image, creates a VM, connects to the VM via communicator (see communicator subsection), and then prepares image by running scripts and actions defined in the provisioners section.  I’m using here two PowerShell scripts for installing IIS role and OS sysprepping at the end of customization. Also, packer automatically updates OS and restarts it if necessary (custom windows-update and built-in windows-restart provisioners)

    "variables": {
        "client_id": "service principal|id here",
        "client_secret": "service principal| secret here",
        "tenant_id": "AD tenant's id here",
        "subscription_id": "subscription's id here"
    "builders": [
            "type": "azure-arm",
            "client_id": "{{user `client_id`}}",
            "client_secret": "{{user `client_secret`}}",
            "tenant_id": "{{user `tenant_id`}}",
            "subscription_id": "{{user `subscription_id`}}",
            "os_type": "Windows",
            "image_publisher": "MicrosoftWindowsServer",
            "image_offer": "WindowsServer",
            "image_sku": "2019-Datacenter",
            "image_version": "latest",
            "managed_image_resource_group_name": "TestRG",
            "managed_image_name": "ws2019-iis",
            "disk_caching_type": "ReadWrite",
            "communicator": "winrm",
            "winrm_use_ssl": true,
            "winrm_insecure": true,
            "winrm_timeout": "20m",
            "winrm_username": "packer",
            "location": "West Europe",
            "vm_size": "Standard_A2_v2",
            "azure_tags": {
                "dept": "IT"
    "provisioners": [
            "type": "powershell",
            "inline": [
                "Write-Host 'Configuring IIS Role and sysprepping...'"
            "type": "powershell",
            "script": "./scripts/iis-install.ps1"
            "type": "windows-update"
            "type": "windows-restart"
            "type": "powershell",
            "script": "./scripts/iis-sysprep.ps1"

When you end up with the configuration file, run packer build and wait while customization steps finish. Packer’s basic steps for a build are:

  • Create a resource group.
  • Validate and deploy a VM template.
  • Execute provision – defined by the user; typically shell commands.
  • Power off and capture the VM.
  • Delete the resource group.
  • Delete the temporary VM’s OS disk.

As a result, image with the name defined in the managed_image_name option will be added to Azure Images service:

packer azure images

Scripts and other stuff will be available on my GitHub soon. Stay tuned.