Deploying VMware vSphere Replication fails at registration with the error: Error applying startup configuration: com.vmware.vr-UUID
search cancel

Deploying VMware vSphere Replication fails at registration with the error: Error applying startup configuration: com.vmware.vr-UUID

book

Article ID: 342601

calendar_today

Updated On:

Products

VMware Live Recovery VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • vSphere Replication was previously deployed and removed from the VMware vCenter Server
  • The vSphere Replication appliance virtual appliance management interface displays this error when you click Save and Restart:

    Error applying startup configuration: com.vmware.vr-UUID
  • The /opt/vmware/hms/hms-configtool.log file shows errors similar to:

    <YYYY-MM-DD>T<time> vsphere.local 2d8652df-8b87-466f-89b6-22f3307575a0 ERROR] [IdentityManager] Failed to delete principalName [com.vmware.vr-UUID] in tenant [vsphere.local]
    <YYYY-MM-DD>T<time> vsphere.local 2d8652df-8b87-466f-89b6-22f3307575a0 ERROR] [ServerUtils] Exception 'com.vmware.identity.idm.InvalidPrincipalException: Principal name: com.vmware.vr-UUID@vsphere.local doesn't exist.'
    com.vmware.identity.idm.InvalidPrincipalException: Principal name: com.vmware.vr-UUID@vsphere.local doesn't exist.
    at com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider.deletePrincipal(VMwareDirectoryProvider.java:4475)
    at com.vmware.identity.idm.server.IdentityManager.deletePrincipal(IdentityManager.java:5256)
    at com.vmware.identity.idm.server.IdentityManager.deletePrincipal(IdentityManager.java:9117)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
    at sun.rmi.transport.Transport$2.run(Transport.java:202)
    at sun.rmi.transport.Transport$2.run(Transport.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:198)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:567)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:828)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.access$400(TCPTransport.java:619)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:684)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:681)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:681)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
    <YYYY-MM-DD>T<time> vsphere.local f4432425-b273-4ecc-8e44-f2b1f5fcf4b9 INFO ] [IdentityManager] Authentication succeeded for user [[email protected]] in tenant [vsphere.local] in [10] milliseconds with provider [vsphere.local] of type [com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider]
    <YYYY-MM-DD>T<time> vsphere.local f1aee3f9-fb10-4d72-974f-c532371e7f03 ERROR] [IdentityManager] Failed to add solution user [com.vmware.vr-UUID] in tenant [vsphere.local]
    <YYYY-MM-DD>T<time> vsphere.local f1aee3f9-fb10-4d72-974f-c532371e7f03 ERROR] [ServerUtils] Exception 'com.vmware.identity.idm.DuplicateCertificateException: Same subjectDN already exists for another solution user'
    com.vmware.identity.idm.DuplicateCertificateException: Same subjectDN already exists for another solution user
    at com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider.addServicePrincipalInternal(VMwareDirectoryProvider.java:2362)
    at com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider.addServicePrincipal(VMwareDirectoryProvider.java:2313)
    at com.vmware.identity.idm.server.IdentityManager.addSolutionUser(IdentityManager.java:2941)
    at com.vmware.identity.idm.server.IdentityManager.addSolutionUser(IdentityManager.java:8469)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
    at sun.rmi.transport.Transport$2.run(Transport.java:202)
    at sun.rmi.transport.Transport$2.run(Transport.java:199)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:198)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:567)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:828)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.access$400(TCPTransport.java:619)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:684)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$1.run(TCPTransport.java:681)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:681)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
    </time></time></time></time></time>

  • The %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\sso\vmware-sts-idmd.log file on the VMware Platform Services Controller contains errors similar to:

    <YYYY-MM-DD>T<time> ERROR com.vmware.vim.sso.client.impl.SoapBindingImpl [main] (..client.impl.SoapBindingImpl)
    | SOAP fault
    javax.xml.ws.soap.SOAPFaultException: Invalid credentials
    at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(Unknown Source)
    at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(Unknown Source)
    at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(Unknown Source)
    at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(Unknown Source)
    at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:130)
    at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:81)
    at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:769)
    at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:699)
    at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:460)
    at com.vmware.jvsl.sso.HokStsService.acquireSolutionToken(HokStsService.java:61)
    at com.vmware.jvsl.sso.HokStsService.acquireSolutionToken(HokStsService.java:56)
    at com.vmware.jvsl.sso.SsoAdminService.deleteSolutionUserImpl(SsoAdminService.java:261)
    at com.vmware.jvsl.sso.SsoAdminService.deleteSolutionUser(SsoAdminService.java:252)
    at com.vmware.jvsl.sso.SsoAdminService$4.run(SsoAdminService.java:243)
    at com.vmware.jvsl.sso.SsoAdminService$4.run(SsoAdminService.java:239)
    at com.vmware.jvsl.sso.SsoAdminService.with(SsoAdminService.java:109)
    at com.vmware.jvsl.sso.SsoAdminService.deleteSolutionUser(SsoAdminService.java:239)
    at com.vmware.hms.apps.util.CreateSolutionUser.doWork(CreateSolutionUser.java:123)
    at com.vmware.hms.apps.util.util.SolutionUserAction.runImpl(SolutionUserAction.java:74)
    at com.vmware.hms.apps.util.util.SolutionUserAction.run(SolutionUserAction.java:44)
    at com.vmware.hms.apps.util.App.run(App.java:83)
    at com.vmware.hms.apps.util.App$1.run(App.java:98)
    at com.vmware.jvsl.run.ExceptionHandlerRunnable$1.run(ExceptionHandlerRunnable.java:47)
    at com.vmware.jvsl.run.CheckedRunnable.withoutChecked(CheckedRunnable.java:19)
    at com.vmware.jvsl.run.ExceptionHandlerRunnable.withExceptionHandler(ExceptionHandlerRunnable.java:43)
    at com.vmware.hms.apps.util.App.main(App.java:94) </time>


Environment

VMware vSphere Replication 6.5.x
VMware vSphere Replication 6.1.x
VMware vSphere Replication 6.0.x

Cause

This issue occurs because an existing vSphere Replication solution user is registered with VMware vCenter Server.

Resolution

To resolve this issue, unregister the previous vSphere Replication extension from vCenter Server.

To unregister an extension from vCenter Server:
  1. Log in to the vCenter Server managed object browser (MOB). The URL for the MOB is https://vCenter_FQDN/mob .
  2. Click content > ServiceContent > content.
  3. Click extensionManager > ManagedObjectReference:ExtensionManager > ExtensionManager.
  4. Under Methods, select void UnregisterExtension.
  5. Click extensionKey (required)string and enter com.vmware.vcHms .
  6. Click Invoke.
  7. Log in to vCenter Single Sign-on as [email protected] .

    Note:Replace vsphere.local with the name of your vCenter Single Sign-on domain if you have defined a custom name.
  8. Navigate to Administration > Users > Solution Users.
  9. Remove the vSphere Replication solution user. This user should contain vr in the user name.
  10. Rerun the registration process for vSphere Replication.


Additional Information

vSphere Replication の新しいデプロイに失敗する - VAMI の登録が次のエラーで失敗する:スタートアップ構成の適用でエラーが発生しました: com.vmware.vr-d5d2cca5-7afd-4a77-966a-af1b3d7f92d0
注册时部署 VMware vSphere Replication 失败并出现以下错误: 应用启动配置时出错: com.vmware.vr-UUID