Share via

SqlIaaSAgent Extension could not be found during SQL Server VM deployment in Azure Stack Development Kit (ASDK)

Ataur Rahman 1 Reputation point
2020-06-12T21:45:34.23+00:00

I have downloaded the Windows Server and SQL Server VMs from the Azure MarketPlace along with the SQL IaaS extension.

I was following the below tutorial to deploy the SQL Server
https://cloudworkshop.blob.core.windows.net/azure-stack/HOL/Hands-on%20lab%20step-by-step%20-%20Azure%20Stack.html

As per this document, I successfully deployed the File Server Virtual Machine in Azure Stack without any problem.

When I tried to deploy the SQL Server VM I was getting below error even though SQLIaasAgentExtension file was downloaded in the azure marketplace:
Error Details:
"code": "ArtifactNotFound"
"message": "Extension with publisher 'Microsoft.SqlServer.Management', type 'SqlIaaSAgent', and type handler version '2.0' could not be found in the extension repository."

Error screenshot:
9879-sqliaasextension-error.png

How can I fix this SqlIaaSAgent Extension problem during SQL Agent deployment to Azure Stack?

Thanks In Advance For Your Support,

Ataur Rahman

Azure Stack Hub
Azure Stack Hub
An extension of Azure for running apps in an on-premises environment and delivering Azure services in a datacenter.
180 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dennis Birk 401 Reputation points
    2020-06-13T09:39:45.21+00:00

    Hi,

    check in the admin portal on the marketplace management the correct version for the extension.

    Check also the requirements for SQL PaaS provider:
    https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-sql-resource-provider-deploy?view=azs-2002

    0 comments
  2. TravisCragg-MSFT 5,681 Reputation points Microsoft Employee
    2020-06-19T10:37:03.953+00:00

    The guide you are using is from 2018, and is several versions behind the current ASDK version. I would follow the guide listed Here for a updated information.

    0 comments
  3. Robert F Sonders 1 Reputation point
    2020-06-25T20:31:29.753+00:00

    @TravisCragg-MSFT
    I have just experienced the same issue. There is a hardcoded value "typeHandlerVersion" that is set differently for the same MArketplace item.
    SQL Server 2017 Enterprise Windows Server 2016 Version: 14.0.20190410
    Set now to 2.0, when it should be set to 1.2</p>
    For the same template version. there were two versions, of the same build, in the marketplace.

    Worth noting... this will fix - AFter the VM deployment. Removing the -Version (which is the typeHandlerVersion)

    Fix for TypeHandler

    Set-AzureRMVMSqlServerExtension -VMName "SQLServer01" -ResourceGroupName "SQL-BDC-management-rg"
    -Name "SQLIaasExtension" -Location "local"; #-Version "1.0"

    0 comments