PowerShell script exchange
Post Reply
GaborCs
Novice
Posts: 7
Liked: 3 times
Joined: Jun 12, 2024 11:40 am
Contact:

[v13] "No grpc-status found on response."

Post by GaborCs »

just upgraded to 13.0.1.180

since there, none of my scipts are running

a simple Get-VBRLocalHost is not working:

from Veeam Backup and Replication PowerShell Toolkit (aka console started from the VBR):
Get-VBRLocalHost
Get-VBRLocalhost: PowerShell environment initialization failed: Failed to connect to Veeam Backup & Replication server:
Status(StatusCode="Cancelled", Detail="No grpc-status found on response.")
any idea? user has got admin rights, all services running
tried with connect-vbrserver with different users/ports - none of them working
david.domask
Veeam Software
Posts: 3096
Liked: 713 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: [v13] "No grpc-status found on response."

Post by david.domask »

Hi GaborCs,

Any chance your AV on the Backup Server does HTTPs traffic scanning? Have seen this when AV or other security software interferes via its https scanning and / or certificate replacement. We saw this with ESET and the Web Access Protection > HTTPs Traffic Scanning > HTTP Traffic Scanning option -- for other AVs it may be called differently, but please check it.
David Domask | Product Management: Principal Analyst
GaborCs
Novice
Posts: 7
Liked: 3 times
Joined: Jun 12, 2024 11:40 am
Contact:

Re: [v13] "No grpc-status found on response."

Post by GaborCs »

Hi David,

thanks for the idea

it was the ESET webprtection

turned off , and voila - Get-VBRLocalHost is working
now i'll try to put all veeam releated things to exceptions

scripst are "not exactly" wroking, but thats another question group :)

thanks for your help
david.domask
Veeam Software
Posts: 3096
Liked: 713 times
Joined: Jun 28, 2016 12:12 pm
Contact:

Re: [v13] "No grpc-status found on response."

Post by david.domask »

Glad it was that simple :) I don't have ESET handy to test with, but if you're able to set an exclusion on the Veeam powershell module / executable itself, it should help.

We did have this noted in the v13.0.1 release notes, but a bit easy to miss -- will ask the TechWriters to please also add it to the Powershell Reference Guide for better visibility.

And for the other items, feel free to make new topic if you're not able to make headway on your own.
David Domask | Product Management: Principal Analyst
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests