Approval for host has failed

[stingray75]

Hi,

In my Data Collection VMware session log (Veeam ONE Reporter -> Configuration -> Sessions) I see the following:

...

Code: Select all

3/6/2015 4:30:45 AM [info]: Getting Objects for approval...
3/6/2015 4:30:47 AM [info]: Objects have been collected.
3/6/2015 4:30:51 AM [warning]: Approval for host vCenter.amer.net.intra\ABC\ABC Prod 1\abchost1.net.intra has failed
3/6/2015 4:30:56 AM [warning]: Approval for host vCenter.amer.net.intra\ABC\ABC Prod 1\abchost2.net.intra has failed
3/6/2015 4:30:57 AM [warning]: Approval for host vCenter.amer.net.intra\ABC\ABC Prod 1\abchost3.net.intra has failed
3/6/2015 4:56:13 AM [info]: Objects have been approved. 5673 custom attributes have been updated.
3/6/2015 5:06:17 AM [info]: Updating SSRS cache
3/6/2015 5:06:17 AM [info]: Data collection completed for all objects.
3/6/2015 5:06:17 AM [info]: Updating report data...
3/6/2015 5:06:17 AM [info]: Updating report data has been completed.

What does "approval for host has failed" mean? Should I raise a support call or is there a quick fix?

Thanks

Matt

[Vitaliy S.]

Hi Matt,

Do you write custom attributes to your vCenter Server? If not, then you can ignore this warning message. Also, our dev team would appreciate, if you could send us debug logs for review.

Thanks!

[stingray75]

Thanks for the quick reply. Yes, we do use custom attributes, and I just found in SchedulingService.log there's an error "Failed to execute SetCustomFieldValueTo command" as you suggested. I know what happened - we used to have a custom attribute "Operational Criticality" which was set to global. We then changed it to Virtual Machine as we decided all ESX hosts are highly critical. But it looks like these 3 hosts still had values set in Veeam, so now Veeam can't write the data back to vCenter. Time to migrate to Tags methinks.

[Vitaliy S.]

Once you do this, please post your case ID, so that I could escalate it directly to devs.

[stingray75]

For anyone else having this issue, here's how I fixed it:

• I went into Business View -> Configuration -> Categories and edited the offending category, and changed object type from Virtual Machine to All.
• Then i went to Workspace and Set Object Type to Host System. I could now see the hosts which incorrectly had Operational Criticality set.
• I selected the hosts, clicked Edit Category and chose re-apply rules so it would set it back to Uncategorized.
• Now back to Configuration -> Categories and set object type back to Virtual Machine, which now matches the setting in vCenter.

[Vitaliy S.]

Wow, that was quick. Thanks for sharing your solution.