qiyuwei
Contributor
Contributor

Windows vCenter vsphere-ui cannot start

Failed start vsphere-ui service after vcenter update.  it caused only flash based web client can connect. HTML5 failed.

Current version is 6.7.0 11727065

Can anyone has idea on this?

conflicts with 'com.vmware.vim.vmomi.core.exception_0.0.1.11059944' in bundle 'com.vmware.vlsi.core_0.0.1.11059944[170]' used by 'com.vmware.vim.binding.cis.cm.monitor_1.0.0' in bundle 'com.vmware.cm.vmodl_1.0.0[1556590240671]'
                package        'com.vmware.vim.vmomi.core_0.0.1.9688497' in bundle 'com.vmware.vlsi.core_0.0.1.9688497[1556590240712]' used by 'com.vmware.cis.services.common.sso_1.0.0' in bundle 'com.vmware.service.common_1.0.0[1556590240726]'
                conflicts with 'com.vmware.vim.vmomi.core_0.0.1.11059944' in bundle 'com.vmware.vlsi.core_0.0.1.11059944[170]' used by 'com.vmware.vim.binding.cis.cm.monitor_1.0.0' in bundle 'com.vmware.cm.vmodl_1.0.0[1556590240671]'

        Uses violation: <Import-Package: com.vmware.vim.vmomi.server.session; version="[0.0.0,1.0.0)"> in bundle <com.vmware.cis.services.inventory.client_6.0.0.SNAPSHOT[1556590240663]>
             Resolver reported uses conflict for import

at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:359)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)
at org.eclipse.virgo.kernel.userregion.internal.InitialArtifactDeployer$ArtifactDeployingRunnable.deployArtifacts(InitialArtifactDeployer.java:164)
at org.eclipse.virgo.kernel.userregion.internal.InitialArtifactDeployer$ArtifactDeployingRunnable.run(InitialArtifactDeployer.java:154)
at java.lang.Thread.run(Thread.java:748)

[2019-04-30T10:10:42.403+08:00] [ERROR] system-artifacts              <UR0002E> User region failed while deploying initial artifacts. Shutting down.
[2019-04-30T10:10:42.457+08:00] [INFO ] System Bundle Shutdown        <KE0010I> Shutdown initiated.
[2019-04-30T10:10:42.530+08:00] [INFO ] System Bundle Shutdown        <TC0002I> Stopping Tomcat.
[2019-04-30T10:10:42.725+08:00] [INFO ] System Bundle Shutdown        <TC0003I> Stopped Tomcat.

0 Kudos
1 Reply
daphnissov
Immortal
Immortal

Strongly recommend you do not use vCenter on Windows any more, especially on 6.7 which makes almost zero sense. Use of the appliance is the only way forward.

0 Kudos