Edit VM settings fails with "An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking retry button"
search cancel

Edit VM settings fails with "An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking retry button"

book

Article ID: 398769

calendar_today

Updated On: 06-19-2025

Products

VMware vCenter Server

Issue/Introduction

  • When attempting to edit VM settings, the task fails with following error.
    An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking retry button.
  • The issue is seen in vCenter Enhanced Linked Mode setup. For instance:
    Log in to VC-A via vSphere-UI.
    Navigate to a VM that resides on VC-B.
    Click "Edit Settings" for that VM returns the following error:
    "An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking retry button."
    If the same VM is managed directly from VC-B, the settings load successfully.

  • vsphere-ui logs from VC-A (/var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log) will show similar to below snippets:

[YYYY-MM-DDThh:mm:ss] [INFO ] agw-token-acq10              r0000246 ###### 200024 c.v.v.s.c.impl.SecurityTokenServiceImpl$RequestResponseProcessor  Request is invalid:
ns0:InvalidRequest: 'ActAs' token is invalid!
[YYYY-MM-DDThh:mm:ss] [ERROR] agw-token-acq10              r0000246 ###### 200024 com.vmware.vim.sso.client.impl.SoapBindingImpl                    SOAP fault com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: 'ActAs' token is invalid! Please see the server log to find more detail regarding exact cause of the failure.
        at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
        at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)
        at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:259)
        at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289)
        at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:198)
        at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:120)
        at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:983)
        at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:902)
        at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByToken(SecurityTokenServiceImpl.java:359)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.lambda$doAcquireTokenByToken$6(Unknown Source)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.invokeStsClient(Unknown Source)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.doAcquireTokenByToken(Unknown Source)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.lambda$acquireTokenByToken$5(Unknown Source)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.invokeRetriable(Unknown Source)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.acquireTokenByToken(Unknown Source)
        at com.vmware.vcenter.apigw.sso.impl.SsoServiceImpl.acquireDelegatedToken(Unknown Source)
        at com.vmware.vcenter.apigw.sso.tokenmgmt.impl.AsyncTokenProvider.acquireDelegatedTokenFromSso(Unknown Source)
        at com.vmware.vcenter.apigw.sso.tokenmgmt.impl.AsyncTokenProvider.acquireLocalToken(Unknown Source)
        at com.vmware.vcenter.apigw.sso.tokenmgmt.impl.AsyncTokenProvider.lambda$createAndRegisterLocalTokenAcquisitionUnit$4(Unknown Source)
        at java.util.concurrent.CompletableFuture.uniAccept(CompletableFuture.java:670)
        at java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:646)
        at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:456)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)

[YYYY-MM-DDThh:mm:ss] [INFO ] agw-token-acq10              r0000246 ###### 200024 c.v.v.s.c.impl.SecurityTokenServiceImpl$RequestResponseProcessor  Request is invalid:
ns0:InvalidRequest: 'ActAs' token is invalid!

Environment

vCenter Server 8.x

Cause

The issue is caused by missing solution user (vsphere-webclient-<VC-Machine ID>), which resulted from VMDIR database inconsistencies across partner nodes in the Enhanced Linked Mode environment.

Resolution

If you encounter the symptoms described above, please contact Broadcom Technical Support for further assistance as the resolution involves modifications to the VMDIR database instance.