SqlSetup: Analysis Services Feature connection

[8Ibarra]

Problem description

I am installing SQL Server 2025 with AS feature. But currently encountering an error when connecting to AS

There we're also a line on the logs that says it detected the AS feature and then fail the deployment when connecting.

I am already using lates versions of SqlServerDsc and SqlServer modules.

Also tried leveraging the property: FeatureFlag: "AnalysisServicesConnection"

This particular error didn't occur on SQL Server 2022 and lower.

Verbose logs

Failed to invoke DSC Set method: PowerShell DSC resource DSC_SqlSetup  failed to execute Set-TargetResource functionality with error message: System.InvalidOperationException: Failed to connect to Analysis Services instance 'mrfmrp-dsql00'. (SQLCOMMON0021) ---> System.Management.Automation.PSArgumentException: Cannot find type [Microsoft.AnalysisServices.Server]: verify that the assembly containing this type is loaded.\r\n   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)\r\n   --- End of inner exception stack trace --- "

DSC configuration

- name: Install SQL Server using DSC
      win_dsc:
        resource_name: "SqlSetup"
        DependsOn: "[WindowsFeature]NetFramework45"
        Action:  "Install"
        InstanceName: "{{ sqlserver_instance_name }}"
        Features: "{{ sqlserver_dsc_features }}"
        SQLCollation: "{{ sqlserver_collation }}"
        SourcePath: "X:\\"
        UpdateEnabled: "{{ sqlserver_patch }}"
        UpdateSource: "{{ sqlserver_source_directory }}\\last_cumulative_updates"
        SecurityMode: "{{ sqlserver_security_mode }}"
        SAPwd_username: "{{ sqlserver_sa_username }}"
        SAPwd_password: "{{ sqlserver_sa_password }}"

        FeatureFlag: "AnalysisServicesConnection"

        SQLSysAdminAccounts: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( sqlserver_admin_accounts | join(',') , 'Administrators' ) }}"
        ASSysAdminAccounts: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( sqlserver_admin_accounts | join(',') , 'Administrators' ) }}"

        # Ansible win_dsc will automatically combine parameters with
        # _username/_password to create a pscredential argument.
        SQLSvcAccount_username: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( sql_svc_acct , 'NT AUTHORITY\\System' ) }}"
        SQLSvcAccount_password: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( sql_svc_pass , 'NT AUTHORITY\\System' ) }}"
        AgtSvcAccount_username: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( agt_svc_acct , 'NT AUTHORITY\\System' ) }}"
        AgtSvcAccount_password: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( agt_svc_pass , 'NT AUTHORITY\\System' ) }}"
        RSSvcAccount_username: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( rs_svc_acct , 'NT AUTHORITY\\System' ) }}"
        RSSvcAccount_password: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( rs_svc_pass , 'NT AUTHORITY\\System' ) }}"
        ASSvcAccount_username: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( as_svc_acct , 'NT AUTHORITY\\System' ) }}"
        ASSvcAccount_password: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( as_svc_pass , 'NT AUTHORITY\\System' ) }}"
        ISSvcAccount_username: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( is_svc_acct , 'NT AUTHORITY\\System' ) }}"
        ISSvcAccount_password: "{{ ( sqlserver_join_with_domain | bool ) | ternary ( is_svc_pass , 'NT AUTHORITY\\System' ) }}"

        InstallSharedDir: "{{ sqlserver_install_dir }}"
        InstallSharedWOWDir: "{{ sqlserver_wow_dir }}"
        InstanceDir: "{{ sqlserver_instance_dir }}"
        InstallSQLDataDir: "{{ sqlserver_system_dir }}"
        SQLUserDBDir: "{{ sqlserver_db_dir }}"
        SQLUserDBLogDir: "{{ sqlserver_log_dir }}"
        SQLTempDBDir: "{{ sqlserver_tempdb_dir }}"
        SQLTempDBLogDir: "{{ sqlserver_tempdb_log_dir }}"
        SQLBackupDir: "{{ sqlserver_backup_dir }}"

        ASDataDir: "{{ as_data_dir }}"
        ASLogDir: "{{ as_log_dir }}"
        ASBackupDir: "{{ as_backup_dir }}"
        ASTempDir: "{{ as_temp_dir }}"
        ASSERVERMODE: "{{ as_server_mode }}"
        ASSvcStartupType: "{{ as_svc_startup_type }}"
        ASCollation: "{{ as_collation }}"

      register: sqlserver_install_state
      no_log: "{{ sqlserver_secure_logging }}"
      tags: install

Suggested solution

Currently exploring

SQL Server edition and version

SQL Server 2025 Developer edition

SQL Server PowerShell modules

sqlserver_ps_modules:
  - StorageDsc
  - SqlServerDsc
  - xNetworking
  - SqlServer

Operating system

Windows

PowerShell version

azure-powershell.4.4.1.msi

SqlServerDsc version

SqlServerDsc: 17.5.0

[johlju]

It seems the type is not available in the PowerShell session as per: Cannot find type [Microsoft.AnalysisServices.Server]

It probably fails at:

SqlServerDsc/source/Modules/SqlServerDsc.Common/Public/Connect-SqlAnalysis.ps1

Line 69 in 449a501

$analysisServicesObject = New-Object -TypeName 'Microsoft.AnalysisServices.Server'

You could try running this in the PowerShell session that runs the DSC resource to make sure the assembly is there at least:

Import-Module SqlServer
Write-Verbose ('{0}' -f ([System.AppDomain]::CurrentDomain.GetAssemblies() | ? Location -like "*AnalysisServices*" | Out-String)) -Verbose

If you do not get any assembly Microsoft.AnalysisServices, try older version of the module SqlServer.

If you get an assembly then try to use it:

$analysisServiceInstance = "<ServerName>\<InstanceName>" # Or, just "<ServerName>" for default instance
$analysisServicesDataSource = "Data Source=$analysisServiceInstance" # Or, if you need credential: "Data Source=$analysisServiceInstance;User ID=$userName;Password=$password"

$null = Import-Assembly -Name 'Microsoft.AnalysisServices' -LoadWithPartialName
analysisServicesObject = New-Object -TypeName 'Microsoft.AnalysisServices.Server'
$analysisServicesObject.Connect($analysisServicesDataSource)

[8Ibarra]

Hello, pls correct me if I'm wrong. Patching would be required to be able to run that on the same session that runs the DSC (during installation).

And also, invalid function occurs when I downgraded the SqlServer version.

Lastly, just want to kindly ask if all the features of SQL Server 2025 testing will be included on the future release of SqlServerDsc?

Thanks! :)

[daniel-chamberland]

I ran into this installing SSAS on a new server. Database Engine installed just fine.

Environment

• SQL Server 2025 Developer Edition (clean install — no prior SQL Server versions on the box)
• SqlServerDsc 17.5.1
• SqlServer PowerShell module 22.4.5.1
• Invoked via Ansible DSC module
• Features: AS, IS
• Instance: Named instance (MULTIDIMENSIONAL mode)

Error

Failed to invoke DSC Test method: System.InvalidOperationException: Failed to connect to Analysis Services instance.
(SQLCOMMON0021)
---> System.Management.Automation.PSArgumentException: Cannot find type [Microsoft.AnalysisServices.Server]: verify
that the assembly containing this type is loaded.

Root Cause?

The default code path in Connect-SqlAnalysis uses
[System.Reflection.Assembly]::LoadWithPartialName('Microsoft.AnalysisServices'), which only resolves assemblies
registered in the GAC.

Older SQL Server versions (2016/2017/2019/2022) registered the AMO client assemblies
(Microsoft.AnalysisServices.dll) in the GAC as part of SSAS installation. On a server with any prior SSAS instance,
LoadWithPartialName finds the assembly and DSC works fine.

SQL Server 2025 does not register the AMO client assemblies in the GAC. On a clean server with only SQL Server
2025 SSAS, the GAC has no Microsoft.AnalysisServices.dll, so LoadWithPartialName returns null, and the subsequent
New-Object -TypeName 'Microsoft.AnalysisServices.Server' fails.

Evidence

Server with SQL Server 2022 (+ older SSAS instances) — AMO in GAC, DSC works:
PS> Get-ChildItem "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.AnalysisServices" -Recurse

v4.0_13.0.0.0__89845dcd8080cc91\Microsoft.AnalysisServices.DLL # SQL Server 2016
v4.0_14.0.0.0__89845dcd8080cc91\Microsoft.AnalysisServices.DLL # SQL Server 2017
v4.0_15.0.0.0__89845dcd8080cc91\Microsoft.AnalysisServices.DLL # SQL Server 2019

Server with only SQL Server 2025 — AMO NOT in GAC, DSC fails:
PS> Get-ChildItem "C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.AnalysisServices" -Recurse -File
(empty — no DLLs)

Workaround

Temporarily register the AMO assemblies from the SqlServer PowerShell module into the GAC before the DSC run:

Add-Type -AssemblyName System.EnterpriseServices
$modulePath = (Get-Module -Name SqlServer -ListAvailable | Sort-Object Version -Descending | Select-Object -First
1).ModuleBase
$publish = New-Object System.EnterpriseServices.Internal.Publish

Get-ChildItem -Path $modulePath -Filter "Microsoft.AnalysisServices*.dll" | ForEach-Object {
    $publish.GacInstall($_.FullName)
    Write-Host "Registered $($_.Name)"
}

To unregister afterward:

  Add-Type -AssemblyName System.EnterpriseServices
  $modulePath = (Get-Module -Name SqlServer -ListAvailable | Sort-Object Version -Descending | Select-Object -First
  1).ModuleBase
  $publish = New-Object System.EnterpriseServices.Internal.Publish

  Get-ChildItem -Path $modulePath -Filter "Microsoft.AnalysisServices*.dll" | ForEach-Object {
      $publish.GacRemove($_.FullName)
      Write-Host "Unregistered $($_.Name)"
  }

Result

After GAC registration, the SqlSetup DSC resource successfully installed AS and IS features on SQL Server 2025 without
modification to SqlServerDsc itself.

[johlju]

Thanks for sharing that workaround.

The default code path in Connect-SqlAnalysis uses [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.AnalysisServices'), which only resolves assemblies registered in the GAC.

The feature flag AnalysisServicesConnection is an attempt to not need to register it in the GAC but that requires that the SqlServer module imports the type (assembly) into the PowerShell session, which it seems it does not do in certain cases, or different versions of SqlServer module does not. The integration tests for Tabular and Multi uses the feature flag successfully. But uncertain if it works because something else has registered an assembly in GAC in the build worker (CI).

SqlServerDsc/source/Modules/SqlServerDsc.Common/Public/Connect-SqlAnalysis.ps1

Lines 65 to 69 in 9fbc7a5

	if ((Test-FeatureFlag -FeatureFlag $FeatureFlag -TestFlag 'AnalysisServicesConnection'))
	{
	Import-SqlDscPreferredModule
	$analysisServicesObject = New-Object -TypeName 'Microsoft.AnalysisServices.Server'

[johlju]

@8Ibarra

Patching would be required to be able to run that on the same session that runs the DSC (during installation).

Yes, or at least a session that mimics the how the resource is run (same permission, etc.)

And also, invalid function occurs when I downgraded the SqlServer version.

Yeah, ws afraid of that. I have seen that older versions of SQL Server can't use newer version of module SqlServer and vice-verse. In the case of LoadWithPartial*() it uses the first assembly it finds, so if having a machine with several installed versions of SQL Server instances with several versions of installed SQLPS modules an unsupported SQLPS (for the target SQL Server instance) can be loaded, resulting in type errors.

Lastly, just want to kindly ask if all the features of SQL Server 2025 testing will be included on the future release of SqlServerDsc?

That is dependent on the SqlServerDsc community (the users of the module) who need to help make sure that happens. I'm happy to review pull requests that the community sends in. 🙂

[8Ibarra]

Hello,

I did try the suggested workaround and still received the same error.

I created a pre-task before the DSC run. Based on the logs, it successfully registered all dll into the GAC.

2026-04-13T05:15:43.6786255Z "host_out": "Registered Microsoft.AnalysisServices.Core.dll\r\nRegistered Microsoft.AnalysisServices.dll\r\nRegistered Microsoft.AnalysisServices.PowerShell.Cmdlets.dll\r\nRegistered Microsoft.AnalysisServices.PowerShell.Provider.dll\r\nRegistered Microsoft.AnalysisServices.Tabular.dll\r\nRegistered Microsoft.AnalysisServices.Tabular.Json.dll\r\n"

It always fails on the post validation. After the resource detected the AS and tries to connect to it -- fails.

2026-04-13T05:31:12.1064541Z "[lydkbl-dsql00]: [[SqlSetup]DirectResourceAccess] Analysis Services feature detected.",
2026-04-13T05:31:12.1065845Z "[lydkbl-dsql00]: [[SqlSetup]DirectResourceAccess] Perform operation 'Query CimInstances' with following parameters, ''queryExpression' = SELECT * FROM Win32_Service WHERE Name = 'MSSQLServerOLAPService','queryDialect' = WQL,'namespaceName' = root\cimv2'.",
2026-04-13T05:31:12.1067152Z "[lydkbl-dsql00]: [[SqlSetup]DirectResourceAccess] Operation 'Query CimInstances' complete.",
2026-04-13T05:31:12.1068417Z "[lydkbl-dsql00]: LCM: [ End Set ] [[SqlSetup]DirectResourceAccess] in 846.7900 seconds.",

I am installing the SQL server 2025 on the VM.

[johlju]

I would suggest after it fails that you login to the server, start a PowerShell session and then run the code the DSC resource tries to use using the same account as the DSC resource is run as, do the workaround then and try to connect manually using the same code as the resource does. To see where it fails and what the error messages are. Do you get the error message Cannot find type [Microsoft.AnalysisServices.Server]: again then the session you run the resource in did not find the assemblies. So manually running everything would rule out if it works manuallu then it is a problem when the DSC resources are run.

[8Ibarra]

Hello, I try to isolate the issue and found out that this error only occurs on SQL Server 2025 Standard Developer Edition. I switched on installing Enterprise Developer Edition with the same configuration and it passes the post validation for AS -- No error occurs.