-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Unable to load Veeam PowerShell Modules in PRTG #78
Comments
Have a look at the comment from Johan: https://mycloudrevolution.com/en/2020/01/27/prtg-veeam-sensor-retrospective/
|
Hi Markus, |
@stoeffel2002 thanks for the confirmation. Just to make sure, as an other user the original script works fine? I have also created a Veeam forum thread regarding this behavior: |
@stoeffel2002 might you please test this version: I have added a small hack to make sure PSModulePath includes Veeam Console. |
Hi Markus, |
Awsome. Thanks for your efforts. I will wait for some additional feedback, just to make sure and the I will merge the PR. |
Sorry we receive only the same generic message in PRTG:
XML: The returned XML does not match the expected schema. (code: PE233) -- JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)
The problem seems to be another. Running the latest script from github gives us the the following log message in the directory C:\ProgramData\Paessler\PRTG Network Monitor\Logs\sensors on the PRTG probe server:
C:\Program Files (x86)\PRTG Network Monitor\custom sensors\EXEXML\PRTG-VeeamBRStats.ps1 : The term
'Disconnect-VBRServer' 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.
At line:1 char:1
No Veeam Modules found, Fallback to SnapIn.
Running de script directly on the probe server with veem management console installed works fine.
Any ideas?
Originally posted by @stoeffel2002 in #77 (comment)
The text was updated successfully, but these errors were encountered: