"HTTPS Status 404" error in Windows 2016 when logging to psc-ui
search cancel

"HTTPS Status 404" error in Windows 2016 when logging to psc-ui

book

Article ID: 305915

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • In Windows Server 2016 installation of PSC / vCenter Server, you see error accessing the vSphere Web Client:
HTTPS status 404
 
  • In the psc-client.log file you see entries similar to:

    [2016-12-23 14:10:16.220] [INFO ] pluginLoader-thread-pool-1 com.vmware.vise.extensionfw.impl.JeePluginLoader - Starting plugin-loader task.^M
    [2016-12-23 14:10:16.221] [INFO ] pluginLoader-thread-pool-1 com.vmware.vise.extensionfw.impl.JeePluginLoader - Finished plugin-loader task.^M
    [2016-12-23 14:10:16.237] [ERROR] pluginLoader-thread-pool-1 com.vmware.vise.util.concurrent.WorkerThread - pluginLoader-thread-pool-1 terminated with exception: ^M
    java.lang.NoClassDefFoundError: java/security/ProtectionDomain^M
    at com.vmware.vise.extensionfw.impl.JeePluginLoader.getDir(JeePluginLoader.java:266)^M
    at com.vmware.vise.extensionfw.impl.JeePluginLoader.getWebAppsDir(JeePluginLoader.java:247)^M
    at com.vmware.vise.extensionfw.impl.JeePluginLoader.processPlugins(JeePluginLoader.java:95)^M
    at com.vmware.vise.extensionfw.impl.JeePluginLoader$1.run(JeePluginLoader.java:161)^M
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)^M
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)^M
    at java.lang.Thread.run(Thread.java:745)^
    Caused by: java.lang.ClassNotFoundException: Illegal access: this web application instance has been stopped already. Could not load [java.security.ProtectionDomain]. The following stack trace is thrown for d
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1315)^
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1178)^M
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1139)^M
    .....
    Caused by: java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [java.security.ProtectionDomain]. The following stack trace is thrown for de
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1325)^M
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1313)^M

    ...
  • In the catalina.2016-12-23.log file, you see entries similar to:

    23-Dec-2016 14:09:48.701 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [psc] appears to have started a thread named [pluginLoader
    java.lang.Thread.sleep(Native Method)
    com.vmware.vise.extensionfw.impl.JeePluginLoader$1.run(JeePluginLoader.java:140)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    java.lang.Thread.run(Thread.java:745)^M

     
  • In the wrapper.log file, you see entries similar to:

    serviceRegistry,i18nManager,tcKissClassLoaderService]; parent: org.springframework.beans.factory.support.DefaultListableBeanFactory@6850a576
    INFO | jvm 1 | 2016/12/23 14:09:48 | ERROR: org.springframework.web.context.ContextLoader - Context initialization failed
    INFO | jvm 1 | 2016/12/23 14:09:48 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vim-services' defined in ServletContext resource [/WEB-INF/spring/platform.xm
    l]: Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ngcSolutionUser' defined in URL [jar:file:/C:/ProgramData/VMware/vCenterServer/runtime/vmware-psc-client/webapps/psc/WEB-
    INF/lib/vim-services-6.0.0.jar!/META-INF/spring/bundle-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vmware.vise.vim.security.sso.impl.NgcSolutionUser]: Constructor threw exception; nested exception is java.lang.UnsatisfiedLinkError: C:\Program Files\VMware\vCenter Server\jre\bin\libvecsjni.dll: Can't find dependent libraries


Environment

VMware vCenter Server 6.5.x

Cause

This issue occurs when java fails to find dependent DLLs of libvecsjni.dll.

Resolution

This is a known issue.
 
Currently, there is no resolution.


Workaround:
To workaround this issue:
  1. Backup the registry.
  2. Rename the key 'Path' to 'Old_Path' in 'HKEY_USERS->S-1-5-18\Environment->Path'.
  3. Reboot the virtual machine.