Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Upgrading to vSphere Web Client 5.5 fails with the error: Error 29107. The service or solution user already registered (2062685)

Symptoms

  • Cannot upgrade to vSphere Web Client 5.5.
  • Upgrading the vSphere Web Client fails.
  • You see an error similar to:

    Error 29107. The service or solution user already registered

  • The vm_ssoreg.log file (located at %TEMP%)contains entries similar to:
14:49:11,232 main INFO com.vmware.vim.install.cli.RegTool] Return code is: AlreadyRegistered
15:01:49,886 main DEBUG com.vmware.vim.install.cli.RegTool] $Id: //depot/vicore/vicore-2013-rel/regtool/viregtool/src/main/java/com/vmware/vim/install/cli/RegTool.java#4 $
15:01:49,892 main DEBUG com.vmware.vim.install.cli.RegTool] Executing command: unregisterSolution -su WebClient_2013.10.17_144456 -d https://<vCenter_Server_FQDN>:7444/lookupservice/sdk -u Administrator@vsphere.local -p *****
15:01:49,959 main INFO com.vmware.vim.install.impl.RegistrationProviderImpl] Intializing registration provider...
15:01:50,968 main DEBUG com.vmware.vim.install.impl.LookupServiceAccess] Creating VMODL client for LookupService
15:01:50,976 main INFO com.vmware.vim.install.impl.CertificateGetter] Getting SSL certificates for https:// vCenter_Server_FQDN:7444/lookupservice/sdk
15:01:51,653 main DEBUG com.vmware.vim.install.impl.CertificateGetter] Establishing socket connection to
vCenter_Server_FQDN;/vCenter_Server_IP_Address;:7444. Timeout is 60000
15:01:53,149 main DEBUG com.vmware.vim.install.impl.AdminServiceAccess] Creating client for SSO Admin on address: https://vCenter_Server_FQDN:7444/sso-adminserver/sdk/vsphere.local
15:01:59,231 main DEBUG com.vmware.vim.install.cli.commands.UnregisterSolutionCommand] First try to delete the authenticated user...
15:01:59,618 main DEBUG com.vmware.vim.install.cli.commands.UnregisterSolutionCommand] The authenticated user cannot be deleted as it is either a person user or doesn't exist any more. Cause: The specified principal (Failed self-deleting a non-solution user '{Name: Administrator, Domain: VSPHERE.LOCAL}') is invalid.
15:01:59,894 main ERROR com.vmware.vim.install.cli.commands.UnregisterSolutionCommand] The specified principal (WebClient_2013.10.17_144456) is invalid.
15:01:59,898 main DEBUG com.vmware.vim.install.cli.commands.UnregisterSolutionCommand]
com.vmware.vim.sso.admin.exception.InvalidPrincipalException: The specified principal (WebClient_2013.10.17_144456) is invalid.
at com.vmware.vim.sso.admin.client.vmomi.impl.VmomiClientCommand.execute(VmomiClientCommand.java:109)
at com.vmware.vim.sso.admin.client.vmomi.impl.VmomiClientCommand.executeEnsuringDomainErrorIs(VmomiClientCommand.java:217)
at com.vmware.vim.sso.admin.client.vmomi.impl.VmomiClientCommand.executeEnsuringDomainErrorIs(VmomiClientCommand.java:199)
at com.vmware.vim.sso.admin.client.vmomi.impl.PrincipalManagementImpl.deleteLocalPrincipal(PrincipalManagementImpl.java:218)
at com.vmware.vim.install.cli.commands.UnregisterSolutionCommand.execute(UnregisterSolutionCommand.java:85)
at com.vmware.vim.install.cli.RegTool.execute(RegTool.java:190)
at com.vmware.vim.install.cli.RegTool.process(RegTool.java:111)
at com.vmware.vim.install.cli.RegTool.main(RegTool.java:38)
15:01:59,902 main INFO com.vmware.vim.install.cli.RegTool] Return code is: UnregisterFailed
  • In the vminst.log file (located at %TEMP%) contains entries similar to:
VMware vSphere Web Client-build-1371037: 14:46:39 C:\Program Files\VMware\Infrastructure\JRE\bin\java.exe -cp "C:\custom\vSphereWebClient\SsoRegTool\*;C:\custom\vSphereWebClient\SsoRegTool" -jar "C:\custom\vSphereWebClient\SsoRegTool\regtool.jar" unregisterSolution -su "WebClient_2013.10.16_180711" -d https:// <vCenter_Server_FQDN>:7444/lookupservice/sdk -u "Administrator@vsphere.local"
VMware vSphere Web Client-build-1371037: 14:46:39 Launching without console output capture.
VMware vSphere Web Client-build-1371037: 14:46:39 Util_Launch::Wait: 1 Hide: 1 TimeOut: -1
VMware vSphere Web Client-build-1371037: 14:46:39 Did not find file/directory: "C:\Program Files\VMware\Infrastructure\JRE\bin\java.exe"
VMware vSphere Web Client-build-1371037: 14:46:39 File "C:\Program Files\VMware\Infrastructure\JRE\bin\java.exe" doesn't exist
VMware vSphere Web Client-build-1371037: 14:46:39 Util_Launch::done Res: 0
VMware vSphere Web Client-build-1371037: 14:46:39 Return code is 31 (successful operation however may not necessarily need return code 0).
VMware vSphere Web Client-build-1371037: 14:46:39 Could not launch SSO Registration tool
VMware vSphere Web Client-build-1371037: 114:46:39 SSO registration tool failed with return code 31
VMware vSphere Web Client-build-1371037: 114:46:39 Please see vm_ssoreg.log in system temporary folder
VMware vSphere Web Client-build-1371037: 14:46:39 Un-registration with SSO failed with return code 31
VMware vSphere Web Client-build-1371037: 14:46:39 Please see vm_ssoreg.log in system temporary folder for details
VMware vSphere Web Client-build-1371037: 14:46:39 End Logging
VMware vSphere Web Client-build-1371037: 14:46:51 Begin Logging

Cause

This issue occurs if your vSphere Web Client and vCenter Single Sign-On services are installed in a custom, non-default location. The vSphere Web Client installer looks for the Java executable in the JRE folder, located by default at C:\Program Files\VMware\Infrastructure\JRE\bin\, but is unable to find it due to the custom installation location. 

Resolution

This issue is resolved in vCenter Server 5.5.0b, available at VMware Downloads. For more information, see the vCenter Server 5.5.0b Release Notes.

To work around this issue, before upgrading your vSphere 5.1 environment to vSphere 5.5, copy the JRE folder from the custom location of vCenter Single Sign-On into the Infrastructure directory (located at: C:\Program Files\VMware\). Once the file has been copied, perform the installation from vSphere 5.1 to vSphere 5.5.

Note: If the error and subsequent rollback has already occurred, perform the installation of the vSphere Web Client 5.5 a second time using its custom location. Due to the cleanup performed by the rollback, the Java executable will be provided during the second attempt of the installation and the existing files in %ProgramData% will be reused.

Update History

12/23/2013 - Added issue resolved in vCenter Server 5.5.0b and added links to the download center and release notes

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: