vSphere client now refusing to connect due to "Unable to read data from the transport connection." error...

[JohnJLewis]

vSphere client refuses to start.  It gives me an "Unable to read data from the transport connection.  The connection was closed." error response.

This configuration was running for about 20 months now.  This just happened all of a sudden, without any obvious stimulus.  Could this be a licensing issue?

I'm able to SSH to the server hosting ESXi and start esxcli.  But I don't know where to go from there.

VMware VSphere client is version 4.1.0 Build 345043.

What is this error telling me?

[HarveyTitanium]

VMware KB: VMware vCenter Server tasks may fail with error: Unable to read data from the transport c...

[JohnJLewis]

I had already looked at that.  I didn't have the IPsec service running.

I was able to get in briefly and saw my VMs.  But no sooner than I did, "PropertyCollector.CreateFilter for object "propertyCollector" failed for some reason.  (See the attached image.)

As you probably already know, I'm not a VMware guru.  I don't know why I'm getting this failure.  Is this a license issue?  Perhaps I'm out of memory?  Any ideas?

Thanks for the response.

[briann55]

I have this same problem.  I wish someone would answer