SPInstallPrereqs: Get-SPDSCAssemblyVersion is not recognized

Details of the scenario you try and problem that is occurring: Today, I saw this error several times:

[[SPInstallPrereqs]InstallPrereqs] Getting installation status of SharePoint prerequisites
The term 'Get-SPDSCAssemblyVersion' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path 
was included, verify that the path is correct and try again.
    + CategoryInfo          : ObjectNotFound: (Get-SPDSCAssemblyVersion:) [], CimException
    + FullyQualifiedErrorId : CommandNotFoundException

The error occurs on the first (and sometimes second) start of a DSC configuration. The issue is reproducible.

The DSC configuration that is using the resource: Shortend configuration

Configuration SharePoint
{
    param( [string]$NodeName  )

    Import-DscResource -ModuleName SharePointDsc -ModuleVersion 1.8.0.0

    node $NodeName
    {
SPInstallPrereqs InstallPrereqs {
            Ensure        = "Present"
            OnlineMode    = $true
            InstallerPath = "$($binaryPath)\Sources\prerequisiteinstaller.exe"
            DependsOn     = @("[Script]DownloadSources", "[Group]LocalAdministrators") 
        }
}
}

Version of the Operating System and PowerShell the DSC Target Node is running: WIN2012R2 PSVersion 5.1.14409.1005

Version of the DSC module you’re using: 1.8.0.0

[ykuijs]

@SvenLauterbach Are you using the DependsOn parameters? Can you share your config? Can you try to add the resources one by one back into your config and try again? I am wondering if there is a specific resource that triggers this issue or maybe a certain number of resources?

Haven’t seen this type of issue before, so not sure what we can do to troubleshoot the issue.

[ykuijs]

This issue is most probably caused by the fact that SQLPS is used and both the SQL and SP resources are using the same PsDscRunAsCredential. More details are described here.

Closing the issue since the solution is to use the SQLServer module instead and SQLPS is no longer updated.

Please add comments if these solutions don’t work, so we can investigate further.