Did you ever find the resolution for this? I just ran into it and the workaround I found worked was to put the engineer doing the work in the local admins on the vCenter server. Same as you I'd given Administrator from within vCenter to this person but they hit the same error.
↧