some backup console's plugins must be updated popup

[oscarm]

I recently updated a couple of VBR servers from 12.1.0.172 to 12.2.0.334. On one of the vbr servers it shows a popup with "some backup console's plug-ins must be updated to the latest version. This requires starting the application under an account with local administrator privileges. Would you like to do this now?"

Off course I clicked on yes and then the vbr console starts like it should and nothing else seem to happen. If I close the console and start again the popup gets shown again. I have looked in programs and features, and as far as I can see all items from veeam have the installation date from when I did the update.

how can I solve this?

I've also created a support ticket (#07417933) for this but I was curious if anyone else came across this and maybe have a solution.

[mauricio]

Interesting. I'm facing the same issue in my development environment.

Look forward to finding out what the actual fix is.

[Heyko]

We have the same issue. I'm also interested in a solution.

[mauricio]

Hello,

If anyone has an update on this, I'd be happy to hear it. Maybe from OscarM?

Thanks!

[FaberfoX]

Just had the same issue, I'll keep an eye on this post for replies before opening a ticket myself.

[nvdwansem]

Seeing the same issue, any update would be appreciated.

I remembered I had a similar issue in the past and looked up some old documentation I made for myself.

In 2017 I solved it by giving domain users or any other group the user is member of full access to the following registry key:

Change the permissions of the following registry key: \\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ -> Users full control.

Not the most clean way I guess but it does solve the problem.

Done some more fiddling around: setting the rights on Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins works as well.

[jotge]

Hello,

I can confirm that the workaround from nvdwansem works very well.

I just don't understand why this is necessary. Above all, a one-time assignment of rights + start de console + update of the plugins is not enough. The user must remain authorized otherwise the message will appear again the next time the console is started.

Fun Fact: We have several environments, I have made about 10 updates so far without this being a problem. The configuration is almost identical in all environments because we have a configuration standard. For example, we almost only use local users as the servers are not members of any domain.

Have a nice day.

[AlexLeadingEdge]

Case # 07540246

I am having the same issue after upgrading to VeeamB&R 12.3.0.310 , closing VeeamBR and opening it again gives the same warning / error.

[Nas]

Same alert received on VBR1 console with 12.2.0.334, when trying to connect to VBR2 which is also 12.2.0.334.

[aceit]

Case # 07540246

I am having the same issue after upgrading to VeeamB&R 12.3.0.310 , closing VeeamBR and opening it again gives the same warning / error.

Same for me after upgrade clicking on the console launch icon on the desktop. Connecting with a user with local machine "administrators" group membership.
If I explicitly "run it as administrator", no message.
But before, in 12.1 I come from, was opening without popup message.

[chrislove]

We could never fix this with changing permissions on reg keys (maybe doing it wrong). Only solution was to identify the mismatched plugin versions between VBR servers and update them to match. Otherwise connecting to a VBR server with different plugin versions than in the reg keys would mean the console wants to update the reg keys again to that VBR servers version. Mainly seems to be an issue on VBR updates because the installer (and support couldn’t really explain this) doesn't seem to keep plugins at a consistent level.

[AlexLeadingEdge]

Veeam Support suggested modifying this registry key, which has fixed the issue for me.

Open the Registry as an administrator and head over to the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

Find the "Plugins" Subkey and right-click on it.

Click on "Permissions"

In the window that opens, please ensure that the "Read" permission is enabled for "Authenticated Users".

If this permission is not present, please add it.

Once added, close the windows and close the Veeam Server UI and then reopen it.

The window warning about available updates should no longer appear.

[aceit]

I confirm, thanks, Read permission is sufficient to fix (maybe the installer doesn't correctly set the permissions).

Strange that, despite being being in local admin groups, still showed if without the registry fix. But with an explicit "run as administrator" on the icon, the warning popup didn't show.
maybe something wrong also in the authority checks?

[Mildur]

Hi all,

Thank you for the feedback and for providing the case number.
Our R&D team will investigate why the permission could have been missing in the first place.

Best,
Fabian

[claudiohipolito]

Hello everyone,

I'm also having this problem when trying to connect the console to the VBR Server. Both are on the same version, 12.3.0.310.

The plugin update popup appears, requiring credentials with administrator privileges. I've already assigned permissions on the read log to the authenticated user group, but I haven't had any success.

Thanks.

Best Regards,

Cláudio Hipólito

[aceit]

Issue still present in 12.3.1.1139 exactly the same ... installing the 12.3.1.1139 pack patch reverted the registry auth workaround fix that I did before.

Please fix in the new installers pls... thx...

[barrnunn]

Open Control Panel - Programs and features on each server and search for "Plug-in". If any of the Veeam Plug-in versions are different this will happen.

[broth]

Veeam Support suggested modifying this registry key, which has fixed the issue for me.

This worked for me! 12.3.1 here, had no issue for the local admin we were using but once we made a second user that wasn't an admin this became an issue. Added the Users group as read only and fixed everything

Thanks!

[c.edwards]

This also worked for us. It has been a very slight irritation for years. It would be nice to see it fixed in the product.