Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

R

rjames1

1 Message

21136

December 30th, 2010 10:00

vWorkspace Error -2145833219

Hello Everyone,

I'm spending the few quiet days over the holiday period playing with vWorkspace 7.2 in my home lab and have run into a strange error message.

"The following error occurred while retrieving the virtual machines or templates from [esxhome]."

"A connection with the server could not be established (-2145833219)"

Which is something of a cryptic error message number.

I'm testing using vSphere 4.1 on a Dell PowerEdge T110, everything is running in a VM including the VC.   My templates are on an iSCSI QNAP storage connected to a dedicated gb switch into the back of the Dell.

I've done the usual poking around and restarted the VM's a few times, checked the passwords ( I like the way vWorkspace validates them on entry ).

Any suggestions ?

DELL-Terry L

29 Posts

December 30th, 2010 16:00

Are the desktop vms Win7? If so, then the -2145833219 error is hex 0x80192EFD which is a generic protocol error. To troubleshoot, log into the console of one of the desktop vms and ping the broker. If an IPv6 address is  returned, then that's the issue. We set the following registry entry on our broker to prefer IPv4 over IPv6:

HKLM\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters\DisabledComponents

REG_DWORD = decimal 32 or hex 20

This doesn't disable IPv6, it just prefers IPv4. Try setting this registry entry on the Win7 desktop for testing, flush the DNS cache ipconfig /flushdns, and reboot the vm.  If successful set the registry value in your desktop template and reprovision.

It this isn't the issue, then turn on broker logging and make several launch attempts and look at the broker log. The vm must communitcate with the broker on both 5203 for heartbeats and 8080 for xml and licensing.

Michel Roth

173 Posts

December 31st, 2010 10:00

In addition to those excellent suggestions by Terry, here are some general suggestions that can help you troubleshoot this:
  • Is the Quest Connection Broker running on all brokers?
  • Are the correct ports open between all Connection Brokers and the vCenter Server(s). View this article for some of the ports (old article but still OK)
  • Is the vCenter Service running?
  • Is DNS working properly? (do the Connection Broker names and vCenter names resolve accordingly IPv4 style?)
Hope this helps.

Was this post helpful?

View All

No Events found!

Top