An administrator reported after January 13th maintenance activity user is receiving error connector unable to reach vCenter. Cannot complete login due to an incorrect user name or password on Port 443.
VMware Live Cyber Recovery 9.0.0.11
Both vCenters are linked this means that they share a single identity database. When a user or service account gets created in one, it is visible in the other. The problem is that the service account naming doesn't account for this because they distinguished with the site id. As a result, VC1 creates svcacct-<siteid> and then VC2 creates svcacct-<siteid> with the same service account name. If these vCenters each had their own identity database, there would be no conflict, but in this case, they end up stomping on each other.
Split the linked VC and create another protected site.