VC 6.5 HTML client - snappyjava.dll on Server 2016 failure

[muhfugen]

I recently installed an evaluation edition of vCenter 6.5 on a Windows Server 2016 Core VM. Everything seems to work fine but when I try click the link for the HTML 5 client I receive the following error

503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:0x000002984f2d3520] _serverNamespace = /ui action = Allow _port = 5090)

I thought perhaps this was due to my use of installing it on a iSCSI mount, or an external MS SQL database, or other reason so I installed it again in a new VM on the C disk with the PostgreSQL database but I still received the error. After checking vsphere-ui-runtime.log I found the following error. It looks like "osname" for "snappyjava.dll" doesnt have an entry for Windows Server 2016, only 8.1 2012 and 2012 R2. Does anyone know what I would need to edit to add Server 2016 to this configuration file? Its rather disappointing that this wont run out of the box on the latest version of Windows Server which has been available to the general public for more than 2 years now. Thanks!

[2016-11-18T02:44:45.740-06:00] [ERROR] fs-watcher	<DE0003E> Install failed for bundle 'com.vmware.h5ngc' version '6.5.0'.
[2016-11-18T02:44:45.742-06:00] [ERROR] fs-watcher	<DE0500E> Unable to install application from URI 'file:/E:/ProgramData/VMware/vCenterServer/runtime/vsphere-ui/server/pickup/h5ngc.war'. Cannot satisfy constraints for bundle 'com.vmware.h5ngc' 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)">
	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">
	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>

. 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)">
	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">
	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>

    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)

[muhfugen]

After finding that that snappyjava.dll was referenced in both C:\ProgramData\VMware/vCenterServer/runtime/vsphere-client/server/work/usr.index and C:\ProgramData\VMware/vCenterServer/runtime/vsphere-ui/server/work/usr.index, and that "Windows NT (unknown)" was listed as an ostype in vsphere-client but no vsphere-ui, and that Java's System.getProperty("os.name") returns "Windows NT (unknown)" on Server 2016 Core, I added that ostype to the usr.index for vsphere-ui. It still isnt working but now the error in vsphere-ui-runtime.log is different: 

[2016-11-18T15:22:57.297-06:00] [INFO ] fs-watcher	<DE0000I> Installing bundle 'com.vmware.h5ngc' version '6.5.0'.
[2016-11-18T15:22:59.369-06:00] [ERROR] fs-watcher	<DE0002E> Installation of bundle 'com.vmware.h5ngc' version '6.5.0' failed. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: commit failed

    at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.CommitStage.process(CommitStage.java:40)

    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.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.osgi.framework.BundleException: Failed to start bundle 'com.vmware.vim-messaging-vsphere' version '6.5.0'

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundle(StandardQuasiFramework.java:386)

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundles(StandardQuasiFramework.java:376)

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.commit(StandardQuasiFramework.java:365)

    at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.CommitStage.process(CommitStage.java:38)

    ... 15 common frames omitted

Caused by: org.osgi.framework.BundleException: The bundle "com.vmware.vim-messaging-vsphere_6.5.0 [254]" could not be resolved. Reason: Missing Constraint: Import-Package: reactor.rx.action; version="0.0.0"

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:292)

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundle(StandardQuasiFramework.java:384)

    ... 18 common frames omitted

[2016-11-18T15:22:59.371-06:00] [ERROR] fs-watcher	<DE0003E> Install failed for bundle 'com.vmware.h5ngc' version '6.5.0'.
[2016-11-18T15:22:59.714-06:00] [ERROR] fs-watcher	<HD0002E> Hot deploy failed for file 'h5ngc.war'. org.eclipse.virgo.nano.deployer.api.core.DeploymentException: commit failed

    at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.CommitStage.process(CommitStage.java:40)

    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.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.osgi.framework.BundleException: Failed to start bundle 'com.vmware.vim-messaging-vsphere' version '6.5.0'

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundle(StandardQuasiFramework.java:386)

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundles(StandardQuasiFramework.java:376)

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.commit(StandardQuasiFramework.java:365)

    at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.CommitStage.process(CommitStage.java:38)

    ... 15 common frames omitted

Caused by: org.osgi.framework.BundleException: The bundle "com.vmware.vim-messaging-vsphere_6.5.0 [254]" could not be resolved. Reason: Missing Constraint: Import-Package: reactor.rx.action; version="0.0.0"

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)

    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)

    at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:292)

    at org.eclipse.virgo.kernel.userregion.internal.quasi.StandardQuasiFramework.startBundle(StandardQuasiFramework.java:384)

    ... 18 common frames omitted

[tbonchev]

There is a workaround for the issue:

Edit the startup arguments of vsphere-ui service to be started with system property os.name=Windows Server 2012 R2.

This can be done by adding the line:

"-Dos.name=Windows Server 2012",

in the StartCommandArgs array in the file

"C:\ProgramData\VMware\vCenterServer\cfg\vmware-vmon\svcCfgfiles\vsphere-ui.json"

After that the service needs to be restarted. It can be done with the following 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

Regards,

Todor

[wayne7215]

Thx tbonchev

I had exactly the same problem after updating from 6.0 to 6.5 and your modification solved the problem!

Regards

Wayne