Set-VBRCredentials isn't working anymore

[manuel.aigner]

Hi there,

We are using a script which synchronizes VBR-Guest credentials between Thycotics Secret Server and VBR. It's running as designed since approx 2 years without any issues.

Code: Select all

PS > get-VBRCredentials -Name $MyUserName | Set-VBRCredentials -User $MyUserName -Password $Secret.obj.Password
Set-VBRCredentials : Object reference not set to an instance of an object.
At line:1 char:40
+ ... yUserName | Set-VBRCredentials -User $MyUserName -Password $Secret.ob ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-VBRCredentials], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Veeam.Backup.PowerShell.Cmdlets.SetVBRCredentials

I checked that all variables/objects are properly filled. And that's the case!

Code: Select all

get-VBRCredentials -Name $MyUserName

returns exactly one VBRCred as expected.

Also if I use Set-VBRCredentials without any params (excepting Cred-Object from pipeline) it ends up in this exception.

It doesn't work via pipelining Get and Set-VBRCred. Also the same error if I save Get-VBRCred return to variable and use Set-VBRCreds -Credential param.

What's going wrong here.
We are using VBR 9.5U4b with an additional private hotfix for corrupted MSSQL-DB restore issues.

[HannesK]

Hello Manuel,
yes, that's a known bug in U4b. Please refer to case #03929711 and ask for the workaround.

The workaround is writing to the database directly instead using the Set-VBRCredentials command.

Best regards,
Hannes

[manuel.aigner]

Hi Hannes,

many thanks for that information. I opened an SR (#03944062)

BR
Manuel

[veremin]

Just so you know - the issue is fixed in version 10. Thanks!