It looks like the vCenter info seems to be incorrect/corrupted/missing.

You can try the steps mentioned in the below EMC KB article and see it it helps in your case.

KB: https://support.emc.com/kb/199317

Note: Before performing the KB resolution steps, take a backup of the existing "mm" and "res" for safe-keeping.

To make a safe-copy:

1) Make sure no backups are running, confirm and then stop the NetWorker services on the NetWorker backup server.

2) Go to the \nsr directory and make a manual copy of "mm" and "res" folders. You can place the copy outside the \nsr directory or have the 'copy' name appended for identification. This is being done so that should anything go wrong, you can replace this copy of "mm" and "res" folders back again into the original location and then bring up the services.

3) Once the copy is done, start the NetWorker services.

4) perform KB steps.

Regards,

Chetan Tikandar

Also kindly let me know if the resolution steps worked by marking my reply as correct answer.

These are the steps mentioned in the KB:

Impact: You are unable to deploy or remove a policy to VM via NMC    

Issue: You are unable to deploy or remove a policy to VM vi NMC.

When you try to apply VBA policy to a VM it give a pop up with message "There are no Policies for this vCenter"

Environment: Networker 8.2, VBA 1.X, 1.1  

Cause: The issue is caused by vcenter configured by wrong name. Check under the EBR appliance properties.

Resolution:

Bring down Networker Services

Connect to nsradmin prompt and check for the "nsr hypervisor" resource

nsradmin -d

nsrdmin> p type: nsr hypervisor;

Delete the effected hyper visor resource. You have to delete the hyper visor offline. (Always keep a backup of the res folder before making any changes to it.)

Bring up the Networker services

Manually create the hyper visor resorce. 

nsradmin

nsrdmin> create type:NSR Hypervisor;name:vCenter_FQDN or ip

Once create run the following command 

nsrdmin> p type: nsr hypervisor;

Update the following proerties using "update" command. 

nsrdmin> update username: username

nsrdmin> update pasword: vc user password

You can change proxy to any desired machine from Networker Server.

(Note : 8.1.X Proxy has to have Windows OS installed. 8.2 can have a non windows VM.) 

nsrdmin> update proxy: FQDN or IP

Once updated try to refresh the VMware view using the F5 key. 

The EMC Support team can also be engaged to help you on the same in case this doesnt work. Anyway, you would have a copy of 'mm' and 'res' so any changes done can be reverted so that you can get back to your configuration that existed before performing the KB steps.

Hi

Yes I have verified user and password for vcenter.

I can see vm:s with policies assinged from Vmware Web client

//Peter

Hi

Done all thoose steps, no change.

Upgraded the NW server to 8.2.1.4, no change.

Will open up a support ticket.

Thanks

Peter

Have you verified the vCenter username and password? Also the vCenter user needs to be have administrator privileges on the vCenter top level.

Regards,

Chetan

Hi

Sorry cannot read the KB :

You Are Not Authorized to View The Content  :-(

//Peter

Hi Peter,

may you verify time on:

backup server

NMC server

Vcenter

VBA

thx

-Nicola

Hi

Time is the same on all !!

//Peter

Is the error Looks like this?

Hi

No, a pop up just says :

there are no Policies for this vCenter

see if this helps.

https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000ycS

Thanks, but...

Access denied

Page you are trying to access is not allowed .. Sorry for inconvenience 

Hi Peter,

Have you got this ever resolved?

We are facing exactly with same issue with two separated vCenter and 2 VBAs

NW 8.2

VBA version 1.1.0.149

Probable Cause :

There are two known issue that can cause this policy not to show up

1.  For any policy group to show up it must be created in MC GUI in the /VirtualCenter/VirtualMachine/ domain.    If they policy is created elsewhere for example /VirtualCenter/ MC domain no policy will show up in the vsphere web client

2.  The policy group are in the correct domain but not showing up for a unknown reason.  This has only been observed if in a upgrade enviroment, where policy were created BEFORE 7.0x upgrade

For the cause mentioned, Solution is as below :

To resolve issue 1. Delete and then recreate the policy in the proper "VirtualMachines" domain

To resolve issue 2. See if any unused ( no  client members) or disabled groups exist,  if they do exists ask the user for permission to delete then re-create the policy groups  and see if the regular policy start to appear in vsphere web client  .  You can use the mccli group show --verbose to capture the policy information  and mccli group add commands to recreate policy with exact same settings