Invalid repositories appearing

[dasfliege]

I've received a fix from support which solved the problem for us. Version now is 8.1.1.2045

[andre.simard]

Same issue as start here also: Repository is invalid.: Exception of type 'System.Exception' was thrown"
Currently on version 8.1.1.159

i will open a case

Thank you

[dloseke]

I'm now having the same issue. All of my immutable Wasabi repos are showing invalid. I have two repo's that are no longer attached to a backup job, that are not immutable, that are still showing up fine. Opened Case 07709446

[dloseke]

After opening a Sev 1 case and getting a quick response with a link to Fix 960459, it looks like I'm good to go again on 8.1.1.2045. Bravo for the quick fix Veeam!

[dasfliege]

I received a fix for another problem we had and since i've installed it, i have 11 repos going invalid state again!
My version is 8.1.1.2052

[evgenich]

With installing version 8.1.1.2045 problem is resolved. Any news when stable official release will come?

[Polina]

It should be included into the next big patch, which I'm expecting in the next few weeks.

[tkutil]

We just started having issues with Backblaze repos for both VBR and V365. Fixed the VBR with new application keys from Backblaze but this trick did not work for V365. Now we cant even add a Backblaze repo in V365.
Running V365 8.1.1.159
Error: Access denied. Could not perform the operation because of missing permissions or wrong data center region.
Case #07715827