VBR Cannot Connect to Data Protection Monitoring & Reporting.

VONE and VBR is on which version?

Does the account you use have local admin privileges on the VBR server (as mentioned in the error message)?

Are all the service up & running on both ends?

Can you verify that all the required FW ports (both directions) are open?

Can you verify that all required AV exclusions are set on both systems?

In case you checked all that (and did the obligatory reboot) maybe you should reach out to Veeam Support.

Best

Lukas

Hi ​@waqasali -

Aside from what ​@Marcel.K and ​@lukas.k suggested, have you gone through the VONE Guide on what is needed/required when adding Data Sources to VONE?

https://helpcenter.veeam.com/docs/one/userguide/backup_server_connect.html?ver=13

VONE 12.3 , VBR 13 

Does the account you use have local admin privileges on the VBR server (as mentioned in the error message)?  yes full access 

Are all the service up & running on both ends?   yes right 

Can you verify that all the required FW ports (both directions) are open?  yes right all ports are open

Can you verify that all required AV exclusions are set on both systems?  currently no AV on system 

All requirements already fulfilled i open a case with support and logs has been sent to support waiting for answer. 

This is not compatible. VONE has to have higher version than VBR

Yes VONE needs to be upgraded 👆

Common sense here. 😉

There’s your answer ​@waqasali , as Marcel & Chris state. Your connection isn’t a supported one, as I believe is shared in the documentation System Requirements 😊

yes you are right i got confirmation from official support that is best for me i will plan for upgradation. 

version conflict as VBR 13 and VONE 12.3 got confirmed by support. 

yes right 

Confirmation email: 

I will prepare plan and implement asap. thank you guys for your comments. 

Hi ​@waqasali just another bit about the issue, in addition to the VONE Version. 

When attempting to add a VBR Server if you using an account with administrator privileges but not “Administrator” you must configure right authorisation for access via WMI. 

check this and this