After upgrade VBR v12 - VeeamOne to VBR = "failed to connect acces denied"

[Jneau]

Hello everyone,

Initially the VBR V11 communicated with Veeamone V12 (last release patched). After updating VBR to V12, no Veeam jobs (except replications I will create another post) but the VeeamOne connection is denied. The AD account used before the v12 update has not been modified (AD and yes it's a constraint..). This account is also used in VEManager and is in the VBR local administrator group. I followed a trail on Veeam.Backup.WmiServer.exe, but nothing happened. I tried to reconnect the VBR to Veeamone several times, but nothing happened. Still the error "failed to connect VBR. access denied".
I can't change the UAC key (Gpo restrictive).
Everything was working before I updated the VBR to v12.
Thanks for your feedback,
Have a good day,
Julian,

[jorgedlcruz]

Hello,
It is very difficult to troubleshoot anything in these forums, and it is not the purpose of replacing support. Please open a support ticket and let us know the ticket ID so we can take a look.

As it is very generic error, and nothing from the logs, the only thing I can say is:
* Check User Permissions: Ensure that the account used by Veeam ONE to connect to the VBR server has the necessary permissions. This account should have administrative privileges on the VBR server.
* Re-enter Credentials: Try re-entering the credentials in Veeam ONE for the VBR server. This can sometimes resolve access issues that occur due to credential mismatches.
* Check Network Settings: Verify that there are no network issues preventing Veeam ONE from connecting to the VBR server. This includes checking firewalls, network policies, and IP configurations.
* Review Logs: Check the logs in both Veeam ONE and VBR for any additional error messages or warnings that might give more insight into the issue.
* Contact Support: If the issue persists, consider contacting Veeam support. They can provide more detailed, step-by-step assistance tailored to your specific environment.

Very generic I know

[Jneau]

Hello Jorge,

Thanks for reply.

I'm going to open a box. But the account permissions haven't changed. Also, the connection between VeeamOne and VBR really broke after the VBR upgrade to V12, Veeamone was already in V12. I'll follow up with support.

Thanks,

[Jneau]

Hello Jorge,

After turning the problem upside down, I finally found the problem, it was a missing Microsoft KB (KB5031361) for windows 2019. https://www.catalog.update.microsoft.co ... =KB5031361.

After installation and reboot, no more credential error.

Julian,

[jorgedlcruz]

Fantastic news,
I will notify QA so we can verify it and add it to our internal knowledge, perhaps even external as well.

Thanks

[chris.childerhose]

@Jorge - it could be related to the DCOM hardening as I had a similar issue recently, and the Support rep sent me this KB - https://www.veeam.com/kb4376

I had to patch my VONE server to be at the same level or higher than the VBR server, and then it connected to VONE.

[jorgedlcruz]

Hi Chris,
It really looks like that error yes, thanks so much for the KB.

That will be very useful for those facing similar issue.

Appreciated it

[chris.childerhose]

Not a problem. Glad the KB will help others.