VMware Horizon Community
emielcarek
Contributor
Contributor
Jump to solution

No Users Can Connect to their VDIs / I am Getting "java.lang.NullPointerException" just after logging in to View Admin or VDI Pool / Unable to Identify the Validity of the Server

Hi guys.

I have  customer running View 5.3 and it's end of life.  I'm hoping that someone can provide some insight.

So, what changed?

I had to manually remove 2 VDIs from view the other day.  I attempted to use the ViewDBChk tool over at VMWare Labs.

- I was getting Java errors when running ViewDBChk, so I installed Java on the Connection server in an attempt to get it running.

- I also attempted to install certificates from the VC server in the trusted root domain store on the Connection server, as I thought it could have been related to it not working.

- I realized that ViewDBChk was not supported in 5.3, and uninstalled Java on the Connection server.

- I manually removed the VDIs, but neglected to remove them from the Composer DB yesterday.  Everything was working as of 5PM last night.

Today, nobody can log in to their view desktops.  They are getting a connection time out or an HTTP 404 error - both externally and internally.

Today, I have removed the 2 VDIs from the Composer DB by following this article: VMware Knowledge Base.

I'm still having issues, and I'm unsure what direction to take.

I'm getting the java.lang error after logging in to View Admin and when I attempt to edit the only pool the customer has.  One of the VDIs is stuck in a provisioning state, but it was working 24 hours ago.  The user on that VDI has had this desktop for a little over a month with no issues.

I've found a lot of references to the "java.lang.NullPointerException", but nothing I have tried seems to help.  What is this error and how can I fix it?  It seems very general and could apply to a lot of things.  The only tip is that I get it when logging in to View admin and when editing the VDI Pool.

Lastly, when attempting to verify server information in View Admin > View Configuration > Servers > vCenter Servers > Edit - I get an error stating: "Server Error - There was an error identifying the validity of the server".  Not sure if this is related, but it's believed to have been working previously.

Some VMware Logs:

2019-03-14T01:29:36.621-04:00 ERROR (0D98-0CCC) <VcCache poller 12e6a565-3b50-4e4e-ac0f-d9b4f221bc13> [AbstractHandler] Problem updating 12e6a565-3b50-4e4e-ac0f-d9b4f221bc13 in VC Cache

2019-03-14T01:29:37.215-04:00 ERROR (0D98-1008) <Publish VC Cert Task-1552541270178> [ServiceConnection25] Problem connecting to VirtualCenter at https://v-center-fqdn.com:443/sdk com.vmware.vdi.vcsupport25.ServiceConnection25.a(SourceFile:630)

2019-03-14T01:29:37.215-04:00 ERROR (0D98-1008) <Publish VC Cert Task-1552541270178> [ServiceConnection25] Problem connecting to VirtualCenter at https://v-center-fqdn.com:443/sdk com.vmware.vdi.vcsupport25.ServiceConnection25.a(SourceFile:630)

java.lang.NullPointerException

at org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:1280)

at java.lang.ClassLoader.getResources(ClassLoader.java:1188)

at org.apache.commons.discovery.jdk.JDK12Hooks.getResources(JDK12Hooks.java:150)

at org.apache.commons.discovery.resource.DiscoverResources$1.getNextResources(DiscoverResources.java:153)

at org.apache.commons.discovery.resource.DiscoverResources$1.getNextResource(DiscoverResources.java:129)

at org.apache.commons.discovery.resource.DiscoverResources$1.hasNext(DiscoverResources.java:116)

at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassNames(DiscoverNamesInFile.java:186)

at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassName(DiscoverNamesInFile.java:170)

at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.hasNext(DiscoverNamesInFile.java:157)

at org.apache.commons.discovery.resource.names.NameDiscoverers$1.getNextIterator(NameDiscoverers.java:143)

at org.apache.commons.discovery.resource.names.NameDiscoverers$1.hasNext(NameDiscoverers.java:126)

at org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.getNextResource(ResourceClassDiscoverImpl.java:159)

at org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.hasNext(ResourceClassDiscoverImpl.java:147)

at org.apache.axis.configuration.EngineConfigurationFactoryFinder$1.run(EngineConfigurationFactoryFinder.java:120)

at java.security.AccessController.doPrivileged(Native Method)

at org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(EngineConfigurationFactoryFinder.java:113)

at org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(EngineConfigurationFactoryFinder.java:160)

at org.apache.axis.client.Service.getEngineConfiguration(Service.java:816)

at org.apache.axis.client.Service.getAxisClient(Service.java:105)

at org.apache.axis.client.Service.<init>(Service.java:114)

at com.vmware.vim25.InternalVimServiceLocator.<init>(InternalVimServiceLocator.java:12)

at com.vmware.vdi.vcsupport25.ServiceConnection25.a(SourceFile:496)

at com.vmware.vdi.vcsupport25.ServiceConnection25.<init>(SourceFile:365)

at com.vmware.vdi.vcsupport25.ServiceConnection25.createInstanceOrFail(SourceFile:325)

at com.vmware.vdi.desktopcontroller.PublishVcCertToSviFederatedTask.a(SourceFile:570)

at com.vmware.vdi.desktopcontroller.PublishVcCertToSviFederatedTask.c(SourceFile:342)

at com.vmware.vdi.desktopcontroller.PublishVcCertToSviFederatedTask.run(SourceFile:257)

at com.vmware.vdi.common.taskmanager.ExecutorImmediate$a.run(SourceFile:55)

2019-03-14T01:29:37.245-04:00 ERROR (0D98-1008) <Publish VC Cert Task-1552541270178> [PublishVcCertToSviFederatedTask] Unable to update VC certificate thumbprints on SVI server https://v-center-fqdn.com:18443 - java.lang.NullPointerException

2019-03-14T01:29:38.853-04:00 ERROR (15B8-10FC) <ABSGC28> [cd] IOException executing request http://127.0.0.1:8123/reset : Connection to http://127.0.0.1:8123 refused com.vmware.vdi.ob.tunnelservice.cd.b(SourceFile:784)

org.apache.http.conn.HttpHostConnectException: Connection to http://127.0.0.1:8123 refused

at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159)

at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)

at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:108)

at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)

at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)

at com.vmware.vdi.ob.tunnelservice.cd.b(SourceFile:780)

at com.vmware.vdi.ob.tunnelservice.cd.f(SourceFile:647)

at com.vmware.vdi.ob.tunnelservice.cd.run(SourceFile:234)

Caused by: java.net.ConnectException: Connection refused: connect

at java.net.DualStackPlainSocketImpl.connect0(Native Method)

at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)

at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:344)

at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

at java.net.Socket.connect(Socket.java:579)

at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)

at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:133)

... 9 more

Thanks in advance for any help!

0 Kudos
1 Solution

Accepted Solutions
emielcarek
Contributor
Contributor
Jump to solution

For anyone who may find this article, I was able to resolve the issue with an uninstall and reinstall of View Connection server.

I took a backup of the Connection server through View Admin.

I took a snapshot of the View server in vSphere.

I made sure that I had the installer with the exact version that was installed.

I uninstalled the VMWare View Connection Server through Add/Remove Programs.

Didn't reboot.

Ran the installer.  It completed and everything started magically working again.

I believe this issue is related to installing Java on the View Server and/or attempting to run ViewDBChk, but I could be wrong.  It appears that it compromised the stability of the environment at the very least.

Thanks!

View solution in original post

0 Kudos
6 Replies
sjesse
Leadership
Leadership
Jump to solution

Did you rename anything like any folders, clusters, or hosts?

0 Kudos
emielcarek
Contributor
Contributor
Jump to solution

Hi sjesse,

No, nothing was renamed.

0 Kudos
sjesse
Leadership
Leadership
Jump to solution

Did a cert change, or expire?Try reconfriming your vcenter settings, just go to the horizon administration panel, and go to View Configuration>Servers and edit the vcenter configuration. You may have to reenter the passwords, but it should reconfirm the ssl thumbprint, which it looks like the error is complaining about.

pastedImage_0.png

0 Kudos
sjesse
Leadership
Leadership
Jump to solution

Sorry I missed the part at the bottom that you already did this. I'd open a ticket, but I'd try restarting the environment

VMware Knowledge Base

0 Kudos
emielcarek
Contributor
Contributor
Jump to solution

No worries, I actually edited the post to include that after posting initially.

I have restarted the environment 3 times today (shutdown Connection and Security servers, reboot Composer Server, power on Connection server, power on Security server).  That didn't work.

I tried to open a case with VMWare, but they told me to come here, as 5.3 is end of life and they won't create a case for it.

I looked at this: VMware Knowledge Base - there is no "locked.properties" file present.  There was no upgrade, so I'm guessing that's why.

I looked at this: VMware Knowledge Base - there are no datastore issues.

And I just tried this: VMware Knowledge Base - No change.

0 Kudos
emielcarek
Contributor
Contributor
Jump to solution

For anyone who may find this article, I was able to resolve the issue with an uninstall and reinstall of View Connection server.

I took a backup of the Connection server through View Admin.

I took a snapshot of the View server in vSphere.

I made sure that I had the installer with the exact version that was installed.

I uninstalled the VMWare View Connection Server through Add/Remove Programs.

Didn't reboot.

Ran the installer.  It completed and everything started magically working again.

I believe this issue is related to installing Java on the View Server and/or attempting to run ViewDBChk, but I could be wrong.  It appears that it compromised the stability of the environment at the very least.

Thanks!

0 Kudos