"Installation of bundle 'com.vmware.h5ngc' version '6.5.0' failed" installing vCenter Server on Windows Server 2016
search cancel

"Installation of bundle 'com.vmware.h5ngc' version '6.5.0' failed" installing vCenter Server on Windows Server 2016

book

Article ID: 301922

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • When you install vCenter Server on Windows Server 2016, you see this error in the vSphere Web Client:

    '503 Service Unavailable'
     
  • In the %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\vsphere-client\logs\vsphere_client_virgo.log file, there are entries similar to:

    [ERROR] fs-watcher org.eclipse.virgo.medic.eventlog.default HD0002E Hot deploy failed for file 'h5ngc.war'.org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Dependency satisfaction failed 
    at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:362)
    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.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)
    at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)
    at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)
    at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)
    at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)
    at java.lang.Thread.run(Thread.java:745)
    Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.vmware.h5ngc' at version '6.5.0': Cannot resolve: com.vmware.h5ngc
    Resolver report:
    A Require-Bundle could not be resolved. Resolver error data <Require-Bundle: com.vmware.vim-messaging-vsphere; bundle-version="0.0.0">. 

    Caused by missing constraint in bundle <com.vmware.h5ngc_6.5.0>constraint: <Require-Bundle: com.vmware.vim-messaging-vsphere; bundle-version="0.0.0">
    An Import-Package could not be resolved. Resolver error data <Import-Package: org.xerial.snappy; version="[1.1.0,2.0.0)">.

    Caused by missing constraint in bundle <io.projectreactor.reactor-core_2.0.3.RELEASE> constraint: <Import-Package: org.xerial.snappy; version="[1.1.0,2.0.0)">
    A bundle could not be resolved because no match was found for the native code specification. Resolver error data <org/xerial/snappy/native/Windows/x86_64/snappyjava.dll; processor=x86-64; osname=win32; osname=Windows Server 2012; osname=Windows Server 2012 R2; osname=Windows 8.1, org/xerial/snappy/native/Windows/x86/snappyjava.dll; processor=x86; osname=win32; osname=Windows Server 2012; osname=Windows Server 2012 R2; osname=Windows 8.1, org/xerial/snappy/native/Mac/x86/libsnappyjava.jnilib; processor=x86; osname=macosx, org/xerial/snappy/native/Mac/x86_64/libsnappyjava.jnilib; processor=x86-64; osname=macosx, org/xerial/snappy/native/Linux/x86_64/libsnappyjava.so; processor=x86-64; osname=linux, org/xerial/snappy/native/Linux/x86/libsnappyjava.so; processor=x86; osname=linux, org/xerial/snappy/native/Linux/arm/libsnappyjava.so; processor=arm; osname=linux, org/xerial/snappy/native/Linux/ppc64/libsnappyjava.so; processor=ppc64; osname=linux, org/xerial/snappy/native/Linux/ppc64le/libsnappyjava.so; processor=ppc64le; osname=linux, org/xerial/snappy/native/AIX/ppc64/libsnappyjava.a; processor=ppc64; osname=aix, org/xerial/snappy/native/SunOS/x86/libsnappyjava.so; processor=x86; osname=sunos, org/xerial/snappy/native/SunOS/x86_64/libsnappyjava.so; processor=x86-64; osname=sunos, org/xerial/snappy/native/SunOS/sparc/libsnappyjava.so; processor=sparc; osname=sunos>. 

    Caused by missing constraint in bundle <org.xerial.snappy.snappy-java_1.1.1.3> constraint: <org/xerial/snappy/native/Windows/x86_64/snappyjava.dll; processor=x86-64; osname=win32; osname=Windows Server 2012; osname=Windows Server 2012 R2; osname=Windows 8.1, org/xerial/snappy/native/Windows/x86/snappyjava.dll; processor=x86; osname=win32; osname=Windows Server 2012; osname=Windows Server 2012 R2; osname=Windows 8.1, org/xerial/snappy/native/Mac/x86/libsnappyjava.jnilib; processor=x86; osname=macosx, org/xerial/snappy/native/Mac/x86_64/libsnappyjava.jnilib; processor=x86-64; osname=macosx, org/xerial/snappy/native/Linux/x86_64/libsnappyjava.so; processor=x86-64; osname=linux, org/xerial/snappy/native/Linux/x86/libsnappyjava.so; processor=x86; osname=linux, org/xerial/snappy/native/Linux/arm/libsnappyjava.so; processor=arm; osname=linux, org/xerial/snappy/native/Linux/ppc64/libsnappyjava.so; processor=ppc64; osname=linux, org/xerial/snappy/native/Linux/ppc64le/libsnappyjava.so; processor=ppc64le; osname=linux, org/xerial/snappy/native/AIX/ppc64/libsnappyjava.a; processor=ppc64; osname=aix, org/xerial/snappy/native/SunOS/x86/libsnappyjava.so; processor=x86; osname=sunos, org/xerial/snappy/native/SunOS/x86_64/libsnappyjava.so; processor=x86-64; osname=sunos, org/xerial/snappy/native/SunOS/sparc/libsnappyjava.so; processor=sparc; osname=sunos>
    An Import-Package could not be resolved. Resolver error data <Import-Package: reactor; version="[2.0.0,3.0.0)">. 

    Caused by missing constraint in bundle <io.projectreactor.reactor-stream_2.0.3.RELEASE> constraint: <Import-Package: reactor; version="[2.0.0,3.0.0)">
    An Import-Package could not be resolved. Resolver error data <Import-Package: reactor; version="0.0.0">. 

    Caused by missing constraint in bundle <com.vmware.vim-messaging-vsphere_6.5.0> constraint: <Import-Package: reactor; version="0.0.0">
  • In the /vcs_logs/vsphere-ui/eventlog.log file, you see entries similar to:

    [2017-03-06T15:19:52.657+01:00] [INFO ] fs-watcher <DE0000I> Installing bundle 'com.vmware.h5ngc' version '6.5.0'. ^M
    [2017-03-06T15:19:57.466+01:00] [INFO ] fs-watcher <ME0003I> Dump 'C:\PROGRA~3\VMware\VCENTE~1\runtime\VSPHER~2\server\serviceability\dump\2017-03-06-15-19-439' generated ^M [2017-03-06T15:19:57.514+01:00] [ERROR] fs-watcher <DE0002E> Installation of bundle 'com.vmware.h5ngc' version '6.5.0' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.vmware.h5ngc' at version '6.5.0': Cannot resolve: com.vmware.h5ngc
    Resolver report: A Require-Bundle could not be resolved. Resolver error data <Require-Bundle: com.vmware.vim-messaging-vsphere; bundle-version="0.0.0">. Caused by missing constraint in bundle <com.vmware.h5ngc_6.5.0> constraint: <Require-Bundle: com.vmware.vim-messaging-vsphere; bundle-version="0.0.0"> An Import-Package could not be resolved. Resolver error data <Import-Package: reactor; version="0.0.0">. Caused by missing constraint in bundle <com.vmware.vim-messaging-vsphere_6.5.0>
    constraint: <Import-Package: reactor; version="0.0.0"> An Import-Package could not be resolved. Resolver error data <Import-Package: org.xerial.snappy; version="[1.1.0,2.0.0)">. Caused by missing constraint in bundle <io.projectreactor.reactor-core_2.0.3.RELEASE> constraint: <Import-Package: org.xerial.snappy; version="[1.1.0,2.0.0)"> A bundle could not be resolved because no match was found for the native code specification.

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.



        Cause

        This issue occurs when the vSphere Web client not able to detect a proper dependency for Java on Windows 2016.

        Resolution

        This is a known issue affecting vSphere 6.5.
         
        This issue is resolved in vCenter Server 6.5c, available at VMware Downloads. For more information, see vCenter Server 6.5.0b Release Notes.


        Workaround:
        To work around this issue, edit the startup arguments of vsphere-ui service:
        1. Open the C:\ProgramData\VMware\vCenterServer\cfg\vmware-vmon\svcCfgfiles\vsphere-ui.json file using a text editor.
        2. Append this line in the StartCommandArgs section:

          -Dos.name=Windows Server 2012
           
        3. Restart the vSphere Web Client services by running these commands:

          C:\Program Files\VMware\vCenter Server\vmon\vmon-cli.exe --stop vsphere-ui

          C:\Program Files\VMware\vCenter Server\vmon\vmon-cli.exe --start vsphere-ui


        Additional Information

        To be alerted when this article is updated, Click Subscribe to Document in the Action box.

        Powered by Wolken Software