Pooran98
Enthusiast
Enthusiast

View Admin reports vCenter server status as "The service is not working properly" after migrating to VCSA 6.5

We a few days ago we upgraded our View Connection servers from 6.2.1 to 7.1.  Then yesterday we migrated our Windows vCenter 6.0 U1 to VCSA 6.5.  After upgrading to VCSA 6.5 in View Administrator it reports that vCenter server status as "The service is not working properly" and the SSL certficate is "Unknown".  This is what we are seeing the logs.  Note I changed the FQDN our vcenter.

2017-05-10T00:00:01.238-04:00 WARN  (0CE4-133C) <Thread-167> [AdminBackendService] Message validation failed, ignoring username param: DOMAIN\XXXXX

2017-05-10T00:00:04.480-04:00 ERROR (0CE4-0834) <VirtualCenterDriver-1222b04e-5961-419f-9ab7-809b8b3b7ee7> [PBMClient] The credentials specified for the Virtual Center do not have the appropriate privilege cn=1222b04e-5961-419f-9ab7-809b8b3b7ee7,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int at https://vcenter:443/sdk

2017-05-10T00:00:04.483-04:00 WARN  (0CE4-0834) <VirtualCenterDriver-1222b04e-5961-419f-9ab7-809b8b3b7ee7> [VirtualCenterDriver] Unable to establish a connection with PBM subsystem <https://vcenter:443/sdk>

2017-05-10T00:00:09.779-04:00 ERROR (0CE4-0834) <VirtualCenterDriver-1222b04e-5961-419f-9ab7-809b8b3b7ee7> [PBMClient] The credentials specified for the Virtual Center do not have the appropriate privilege cn=1222b04e-5961-419f-9ab7-809b8b3b7ee7,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int at https://vcenter:443/sdk

2017-05-10T00:00:09.780-04:00 WARN  (0CE4-0834) <VirtualCenterDriver-1222b04e-5961-419f-9ab7-809b8b3b7ee7> [VirtualCenterDriver] Unable to establish a connection with PBM subsystem <https://vcenter:443/sdk>

1 Reply
Pooran98
Enthusiast
Enthusiast

The issue for us ended up being AD related.  During the migration to VCSA 6.5 it failed to join the AD.  We manually re-joined the AD.  Our Horizon View service account was not working so View could not talk to vCenter thus the error message in View Admin.  We ended up un-joining the VCSA from AD and resetting the computer account.  Then re-joined the AD and added in our identity sources.  Last step was to add the service account to the administrator group in Global Permissions section.  Once we did View could talk to the VCSA.