Failed to Load Module Veeam.Backup.Powershell

[Markus.K1985]

Hello,

a few users of my scripts reported issues like that:

It seems I’ve found the cause of the issue. For some reason PRTG won’t find the module when using: Import-module -name Veeam.Backup.Powershell as it claims it can’t find it.
However, if I after “-name”, specify the complete path to the Veeam.Backup.Powershell.dll, the script is successful. So the script is working fine and as intended, and the issue seems to be on our server and it’s ability to load the Module at times.

Not all have tried to import the dll, but all have the situation where the module does not seem to be available to all users.

Has anyone seen something similar?

Best Wishes
Markus

[johan.h]

I've seen this with other modules too, sometimes you'll have to specify the exact path, if it isn't available as part of the system environment variables.

https://docs.microsoft.com/en-us/powers ... rshell-7.1

[MichaelCade]

Yes in my automation scripts I used

Import-module -name "C:\Program Files\Veeam\Backup and Replication\Console\Veeam.Backup.PowerShell\Veeam.Backup.PowerShell.psd1"

this is ran in the same shell when the unattended installation has completed. Then a new PowerShell window is open to run the Veeam configuration script

[Markus.K1985]

Thanks for the hint and the feedback.

I will see if this hack makes it a bit more robust:

Code: Select all

    # Make sure PSModulePath includes Veeam Console
    $MyModulePath = "C:\Program Files\Veeam\Backup and Replication\Console\"
    $env:PSModulePath = $env:PSModulePath + "$([System.IO.Path]::PathSeparator)$MyModulePath"
    if ($Modules = Get-Module -ListAvailable -Name Veeam.Backup.PowerShell) {
        try {
            $Modules | Import-Module -WarningAction SilentlyContinue
            }
            catch {
                throw "Failed to load Veeam Modules"
                }
        }