Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup Proxy Section: The term 'Get-VBOProxyPool' is not recognized as the name of a cmdlet #47

Open
3 tasks done
Chugdogg opened this issue Nov 12, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Chugdogg
Copy link

Veeam Backup for Microsoft 365 version

7

Bug description

WARNING: [ 07:01:01:327 ] [ Document ] - Backup Proxy Section: The term 'Get-VBOProxyPool' 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.

Command-line input

New-AsBuiltReport -Report Veeam.VB365 -Target SVR-VeeamO365 -Credential $Creds -Format Html,Text -OutputFolderPath 'C:\Report' -EnableHealthCheck

Steps to reproduce

  1. Installed module
  2. Ran mentioned command-line input multiple times and received the same warning and the process just hangs

Expected behaviour

The report to generate as expected

Screenshots

image

Operating System

Server 2019

PowerShell Version

Name Value


PSVersion 5.1.17763.6414
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.6414
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

PowerShell Modules

Name Version


AsBuiltReport.Core 1.4.0
AsBuiltReport.Veeam.VB365 0.3.7
PScribo 0.10.0

Additional Context

No response

Before submitting

@Chugdogg Chugdogg added the bug Something isn't working label Nov 12, 2024
@rebelinux
Copy link
Collaborator

Can you add the -Verbose option to the command and report which section it gets stuck at?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants