Provider method implementation threw unexpected exception: com.vmware.vapi.std.errors.Unauthorized: Unauthorized.In /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log in vCenter we see the below events :
[INFO ] io-127.0.0.1-5090-exec-19207 70768460 125660 201506 c.v.v.c.p.impl.ProvisioningResourcePoolMutationProvider Initiate deployment of template on resource pool. template = file:///VMware-vRealize-Log-Insight-8.18.3.0-24515748.ovfIn /var/log/vmware/vpxd/vpxd.log in vCenter we see the below events :
[WARN ] io-127.0.0.1-5090-exec-19199 70768484 125660 201506 c.v. vsphere. client. provisioning. ovf. impl. OvfDeployServiceImplwaitForSession : reached terminastate ERROR while waiting for IMPORT FILE TRANSFER
[ERROR] io-127.0.0.1-5090-exec-19199 ####### ###### ###### c. v. vsphere. client . provisioning. ovf. impl. OvfDeployService Impl
OVF import session entered ERRORstate. com. vmware. vsphere. client . provisioning.ovf.OvfSessionError: Provider method implementation threw unexpected exception: com. vmware. vapi. std. errors. Unauthorized: Unauthorized (com.vmware . vapi . std. errors. unauthorized) => {
messages = [LocalizableMessage (com. vmware. vapi. std. localizable_message) => {
id = vapi. security. authorization. invalid,
defaultMessage = Unable to authorize user,
args = [],
arams = <null>,
localized = <null>
}],
data = <null>,
errorType = UNAUTHORIZED
at com. vmware. vsphere. client .provisioning. ovf. impl. OvfDeployService Impl. deployOvf (OvfDeployServiceImpl. java : 297)
at sun. reflect. GeneratedMethodAccessor12075. invoke (Unknown Source)
VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.x
This issue is seen in following situations, when.
Mandatory precaution:
In Enhanced Linked Mode (ELM) environment, data consistency is critical. Failure to follow these steps can result in permanent replication divergence.
Shutdown All Nodes: Gracefully shut down every vCenter Server within the SSO domain simultaneously.
Take Snapshots: Take a snapshot of each node while it is powered off.
Note: This ensures that no replication occurs during the snapshot process, preserving a synchronized database state.
Power On: Once all snapshots are complete, power on the vCenter Servers.
Reversion Policy: Should a rollback be necessary, all nodes must be reverted to these powered-off snapshots to maintain replication integrity.
Steps to follow to resolve the issue: