Skip to main content

The command was found in the module PowerShellGet, but the module could not be loaded.

While testing a PowerShell DSC script deployed by Azure Automation on an Azure Virtual Machine I ran against the following error message: 

The command <command> was found in the module PowerShellGet, but the module could not be loaded.

What I tried to accomplish was automatically installing the PowerShell Az modules with the following PowerShell DSC script.

# Import DSC modules
Import-DscResource -ModuleName "PowerShellGet" -ModuleVersion 2.2.5

Node $AllNodes.NodeName
{
  PSModule "Az" {
    Ensure             = "Present"
    Name               = "Az"
    Repository         = "PSGallery"
    InstallationPolicy = "Trusted"
    AllowClobber       = $true
    Force              = $true
    RequiredVersion    = 5.6.0
  }
}

To solve this issue you also have to import the PackageManagement module because PowerShellGet has a dependency on this module. The correct version of the script is thus:

# Import DSC modules
Import-DscResource -ModuleName "PackageManagement" -ModuleVersion 1.4.4
Import-DscResource -ModuleName "PowerShellGet" -ModuleVersion 2.2.5

Node $AllNodes.NodeName
{
  PSModule "Az" {
    Ensure             = "Present"
    Name               = "Az"
    Repository         = "PSGallery"
    InstallationPolicy = "Trusted"
    AllowClobber       = $true
    Force              = $true
    RequiredVersion    = 5.6.0
  }
}

Update (March, 15th)

The PowerShellGet module has a specific dependency on version 1.4.4 of the PackageManagement module. You can see it defined in the manifest file (PowerShellGet.psd1).

RequiredModules   = @(@{ModuleName = 'PackageManagement'; ModuleVersion = '1.4.4' })

Comments

Popular posts from this blog

CS8357: The specified version string contains wildcards, which are not compatible with determinism.

Today I was busy with creating a WCF service solution in Visual Studio Enterprise 2017 (15.9.2). In this solution I use a few C# class libraries based on .NET 4.7.2. When I compiled the solution I got this error message: Error CS8357: The specified version string contains wildcards, which are not compatible with determinism. Either remove wildcards from the version string, or disable determinism for this compilation The error message is linking to my AssemblyInfo.cs file of the Class library projects. In all the projects of this solution I use the wildcard notation for generating build and revision numbers. // Version information for an assembly consists of the following four values: // // Major Version // Minor Version // Build Number // Revision // // You can specify all the values or you can default the Build and Revision Numbers // by using the '*' as shown below: // [assembly: AssemblyVersion("1.0.*")] [assembly: AssemblyVersion("1.0....

Fixing HTTP Error 401.2 unauthorized on local IIS

Sometimes the Windows Authentication got broken on IIS servers so you cannot log in locally on the server. In that case you get the dreadfully error message HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers. To fix this issue you can repair the Windows Authentication feature with the following PowerShell commands: Remove-WindowsFeature Web-Windows-Auth Add-WindowsFeature Web-Windows-Auth

Assign an existing certificate to your IIS website with WiX

Recently I had to change the bindings of existing IIS hosted websites and APIs from HTTP to HTTPS. They are installed with a MSI file created with the WiX Toolset . Because I have to use an already on the server installed certificate I cannot use the Certificate element from the IIS Extension because this element only supports installing and uninstalling certificates based on PFX files. After doing some research I found the blog article Assign Certificate (Set HTTPS Binding certificate) to IIS website from Wix Installer which described the usage of Custom Actions for this purpose. I adopted this approach and rewrote the code for my scenario. With WiX I still create the website. <iis:WebSite Id="WebSite" ConfigureIfExists="yes" AutoStart="yes" Description="MyWebsite" Directory="IISROOT" StartOnInstall="yes"> <iis:WebAddress Id="WebSite...