Quantcast
Channel: VMware Communities: Message List - vCenter™ Server
Viewing all articles
Browse latest Browse all 15787

Upgrade Vcenter from 5.0 to 5.1 update 2: vsphere web client failed to install

$
0
0

I 'm doing an upgrade of vcenter server (2008R2, 8 GB RAM, 80 GB disk) from 5.0 to 5.1 update 2 release.

Single Sign ON, Inventory Service, vCenter Server and vSphere Client components are OK.

When I'm installing the vSphere Web Client component setup stops with an error while Registering with Lookup Service:

Product: VMware vSphere Web Client -- Error 29113.Wrong input - either a command line argument is wrong, a file cannot

be found or the spec file doesn't contain the required information, or the clocks on the two systems are not synchronized.

Check vm_ssoreg.log in system temporary folder for details.

If I check the vm_ssoreg.log there is a SSL error validating a certificate:

 

[2014-07-08 15:39:43,568 main  DEBUG com.vmware.vim.install.impl.RegistrationProviderImpl] Establishing socket connection to SRVVRC002.intraosa.net/10.9.11.121:7444. Timeout is 60000

[2014-07-08 15:39:45,271 main  INFO  com.vmware.vim.install.cli.commands.RegisterServiceCommand] Service with name 'VMware Log Browser' was registered with ID: '{A3E0CD5E-3D08-4F48-8C3D-EA553AF5EF50}:9'

[2014-07-08 15:39:45,271 main  INFO  com.vmware.vim.install.cli.commands.RegisterServiceCommand] Appending serviceId to file

[2014-07-08 15:39:45,474 main  ERROR com.vmware.vim.install.cli.commands.RegisterServiceCommand]

com.vmware.vim.binding.vmodl.fault.InvalidArgument:

invalidProperty = Invalid certificate

inherited from com.vmware.vim.binding.vmodl.fault.InvalidArgument

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

    at java.lang.reflect.Constructor.newInstance(Unknown Source)

    at java.lang.Class.newInstance0(Unknown Source)

    at java.lang.Class.newInstance(Unknown Source)

    at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:171)

    at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:26)

    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:33)

    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:135)

    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:98)

    at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:84)

    at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:37)

    at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:97)

    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:245)

    at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:203)

    at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:126)

    at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:98)

    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:526)

    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:507)

    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:295)

    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:265)

    at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:169)

    at com.sun.proxy.$Proxy23.registerService(Unknown Source)

    at com.vmware.vim.install.cli.commands.RegisterServiceCommand.execute(RegisterServiceCommand.java:54)

    at com.vmware.vim.install.cli.commands.CompositeCommand.execute(CompositeCommand.java:38)

    at com.vmware.vim.install.cli.RegTool.execute(RegTool.java:171)

    at com.vmware.vim.install.cli.RegTool.process(RegTool.java:90)

    at com.vmware.vim.install.cli.RegTool.main(RegTool.java:33)


I added to the vcenter local machine Trusted Root Certicate Autorities both the Lookup Service Certicate and the vcenter server Cerificate rui.crt under the

C:\programData\VMware\VMware VirtualCenter\SSL, so that browsing to these services url I have no certicate warning.

Any hints to solve this problem? I've read many similar posts, but I haven't find a solution yet.

Thanks in advance, Antonio


Viewing all articles
Browse latest Browse all 15787

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>