I creating two separate threads, T1 and T2 then calling T1.connect(windows xp sp2) and T2.connect(windows 2000 server). Then when calls T2.Disconnect, T1 handle is invalidated as well.
If do not release handle there will be no problem
error in follow API function:
VixVM_GetRootSnapshot(...)
thanks!
I ran into that same problem as well. I got a response from someone on the VMware team saying that this is known behavior and that calling HostConnect() just once for both threads then disconnecting after both threads are finished doing what they do is a workaround for this issue until they patch it.
This problem has been reported to death on this forum, here and here and here There's no workaround for connecting to multiple VMs in parallel as far as I know, but there's a workaround forcing disconnect and GC for doing this sequentially. If by any accident you find a workaround for this, please do let us know.