kublikhan Tracker

Re: There was an error in communication

kublikhan — Wed, 26 Oct 2011 00:16:10 GMT

No, the client machine and esx server are not on the same subnet. They are not even in the same country. The datastore is on a different subnet as well, but it's on the same router. Putting all of the machines on the same subnet is not a viable solution for us. Does VIX require all clients, esx servers, and datastores to be on the same subnet? Here is the log files:

vmware-vix:
Oct 25 23:58:12.178: app-2268| Log for Vix pid=5804 version=-1 build=build-368992 option=Release
Oct 25 23:58:12.178: app-2268| The process is 32-bit.
Oct 25 23:58:12.178: app-2268| Host codepage=windows-1252 encoding=windows-1252
Oct 25 23:58:12.178: app-2268| Foundry Init: setting up global state (0 threads)
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: vixLogLevel = 0
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: vixApiTraceLevel = 0
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: vixDebugPanicOnVixAssert = 0
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: vixLogRefcountOnFinalRelease = 0
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: asyncOpWarningThreshold = 1000000
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: enableSyncOpSelection = FALSE
Oct 25 23:58:12.178: app-2268| Vix_InitializeGlobalState: enableExternalThreadInterface = TRUE
Oct 25 23:58:12.178: app-2268| LOCALE windows-1252 -> NULL User=409 System=409
Oct 25 23:58:12.178: app-2268| VixHost_ConnectEx: version -1, hostType 5, hostName https://<myip>/sdk, hostPort 0, options 528
Oct 25 23:58:12.178: app-2268| HOSTINFO 28779581451581 @ 2864716Hz -> 0 @ 1000000Hz
Oct 25 23:58:12.178: app-2268| HOSTINFO ((x * 2998529205) >> 33) + -10046224981807
Oct 25 23:58:12.178: app-4696| HOSTINFO 28779581451665 @ 2864716Hz -> 0 @ 1000000Hz
Oct 25 23:58:12.178: app-4696| HOSTINFO ((x * 2998529205) >> 33) + -10046224981836
Oct 25 23:58:13.968: app-4696| Vix: [4696 vixVIMProxy.c:3449]: VixVIMVmRequestTicketImpl: requesting old-MKS ticket for VM '[datacenter-2/shared1] CPXAV1100/CPXAV1100.vmx'
Oct 25 23:58:35.249: app-1704| Cannot connect to server myserver.com:902: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respondCnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed
Oct 25 23:58:35.249: app-1704| CnxConnectAuthd: Returning false because CnxAuthdConnect failed
Oct 25 23:58:35.249: app-1704| Cnx_Connect: Returning false because CnxConnectAuthd failed
Oct 25 23:58:35.249: app-1704| Cnx_Connect: Error message: Failed to connect to myserver.com:902
Oct 25 23:58:35.249: app-1704| Vix: [1704 foundryVMPowerOps.c:5567]: Error VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMOpenSocketToVMXThroughAuthd(): unable to contact authd: 'Failed to connect to server myserver.com:902'
Oct 25 23:58:35.249: app-4696| Vix: [4696 foundryVMPowerOps.c:5046]: Error VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMFinishConnectingToVMX(): failing open because we can't contact authd
Oct 25 23:58:35.249: app-4696| VixVM_FinalRelease: Close VM socket.

vmware-vixWrapper:
Oct 25 23:58:12.108: app-2268| Log for VixWrapper pid=5804 version=1 build=build-368992 option=Release
Oct 25 23:58:12.108: app-2268| The process is 32-bit.
Oct 25 23:58:12.108: app-2268| Host codepage=windows-1252 encoding=windows-1252
Oct 25 23:58:12.108: app-2268| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX\\ws_server_esx-4\32bit\vix.dll'
Oct 25 23:58:12.108: app-2268| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX\\ws_server_esx-4\32bit\vix.dll'
Oct 25 23:58:12.108: app-2268| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX\\ws_server_esx-4\32bit\vix.dll'
Oct 25 23:58:12.108: app-2268| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX\\ws_server_esx-4\32bit\vix.dll'
Oct 25 23:58:12.111: app-2268| Loading Vix implementation library C:\Program Files (x86)\VMware\VMware VIX\\VSphere-4.1\32bit\vix.dll

I thought maybe it was because one of the ports was not open. But I checked both ports 443 and 902 and it looked like the ports are open:
C:\>C:\PortQryV2\PortQry.exe -n <myip> -e 443
Querying target system called:
<myip>
Attempting to resolve IP address to a name...
IP address resolved to <myip>
querying...
TCP port 443 (https service): LISTENING

C:\PortQryV2\PortQry.exe -n <myip> -e 902
Querying target system called:
<myip>
Attempting to resolve IP address to a name...
IP address resolved to <myip>
querying...
TCP port 902 (unknown service): LISTENING

There was an error in communication

kublikhan — Wed, 22 Jun 2011 21:24:06 GMT

ESX version: 3.5 U4

VIX version: latest

Command run:

C:\Program Files (x86)\VMware\VMware VIX>vmrun -T esx -h https://172.17.235.10/sdk -u serveruser -p serverpass -gu administrator -gp guestpass runProgramInGuest "[shared2] APDNA1101/APDNA1101.vmx" c:\windows\notepad.exe
Error: Cannot open VM: [shared2] APDNA1101/APDNA1101.vmx, There was an error in communication=

We are having a problem connecting to an ESX 3.5 U4 server with VIX. Snapshot is reverted ok, image powers up ok, but cannot connect to the guest image with VIX. We can copy files to the image without issue however. Any ideas what could be wrong here?

Re: Best way to programmatically get installed VIX version

kublikhan — Fri, 01 Oct 2010 18:50:55 GMT

Sorry for not getting back to you on this, but this issue popped up again. I tried VIX_PROPERTY_HOST_SOFTWARE_VERSION but got an error "undeclared identifier". I tried searching around for this property for more information but could not find any other reference to this. Was the property added in a more recent version of VIX? My version may be a few revisions behind.

Best way to programmatically get installed VIX version

kublikhan — Wed, 12 May 2010 22:39:25 GMT

Anyone know the best to to programmatically get the installed version of VMWare VIX and VMWare Workstation on a client machine? I was thinking of looking at the version info on VixCOM.dll for vix and vmware.exe for workstation, but then I don't know what directory it might be installed to on the client machine. I could try the default location, but if they installed to a custom location that would fail.

statically linking VIX libraries

kublikhan — Fri, 05 Feb 2010 21:13:40 GMT

I compiled my code to use the VIX wrapper, which dynamically loads the proper VIX libraries. However this requires that VIX to be installed manually on every machine we run on.

The documentation gives an example of statically linking with the VIX libraries for Workstation. But we need to support all vmware products. Can you statically link to all of the various versions of the VIX libraries, or is this going to cause a conflict?

if not, are we allowed to redist all of the required VIX libraries with our app? Or is this going to violate some terms in the EULA? If allowed,what would be the best way to do this, bundle the VIX SDK with our app and silently install it?

Re: Errors 22002 and 22003 with VixHost_Connect()

kublikhan — Thu, 04 Feb 2010 03:26:31 GMT

After installing VIX on my test machine the problem went away. Thanks!

I misread the documentation. I thought player came with vix, but the doc says only workstation and server install vix.

Errors 22002 and 22003 with VixHost_Connect()

kublikhan — Thu, 04 Feb 2010 02:24:20 GMT

I am getting started working with the vmware API's. I wrote a c++ tool that calls them. It is working fine on my build machine with both VMware Workstation and our ESX server. However when I copy the tool to a test machine that has VMware Player installed, I can't get either player or the esx server working. Is there something additional I have to install on my test box to get this working? Is there something else that I have to change in my linker settings?

Build system:

Windows 7

VIX 1.8.1.10141

VMware Workstation 6.5.1.5078

Test system:

Windows XP SP2

Vmware Player 3.0.0.9911

ESX Server:

VMWare ESX Server 3i, 3.5.0, 111522

code:

m_ConnType = VIX_SERVICEPROVIDER_DEFAULT;

m_jobHandle = VixHost_Connect(VIX_API_VERSION, m_ConnType, W2A(lpsHostName), 0, W2A(lpsHostUser) , W2A(lpsHostPassword), 0, VIX_INVALID_HANDLE, NULL, NULL);

m_err = VixJob_Wait(m_jobHandle, VIX_PROPERTY_JOB_RESULT_HANDLE, &m_hostHandle, VIX_PROPERTY_NONE);

Runtime results:

Build machine: Both workstation and esx server work fine.

Test machine with esx server: Error 22002 – VIX_E_WRAPPER_VERSION_NOT_FOUND

The specified version was not found.

Test machine with Player: Error 22003 – VIX_E_WRAPPER_SERVICEPROVIDER_NOT_FOUND

The specified service provider was not found.

I have also tried setting the connection type to either VIX_SERVICEPROVIDER_VMWARE_VI_SERVER, VIX_SERVICEPROVIDER_VMWARE_WORKSTATION, or VIX_SERVICEPROVIDER_VMWARE_PLAYER, but the same error occurs.

Test machine Log File:

Feb 03 18:38:42.752: app-3892| Log for VixWrapper pid=3876 version=1 build=build-207905 option=Release

Feb 03 18:38:42.752: app-3892| The process is 32-bit.

Feb 03 18:38:42.752: app-3892| Host codepage=windows-1252 encoding=windows-1252

LOG NOT INITIALIZED | W32Util_IsDirectorySafe: Failed DACL num entries check, "..."

Feb 03 18:38:42.752: app-3892| Error: VIX wrapper config file (null)\vixwrapper-config.txt not found.

Feb 03 18:38:42.752: app-3892| Failed to load wrapper configuration file

Feb 03 18:38:42.752: app-3892| config points to non-existent implementation library '(null)\ws_server_esx-4\32bit\vix.dll'

Feb 03 18:38:42.752: app-3892| config points to non-existent implementation library '(null)\ws-5\32bit\vix.dll'

Feb 03 18:38:42.752: app-3892| config points to non-existent implementation library '(null)\ws-3\32bit\vix.dll'

Feb 03 18:38:42.752: app-3892| config points to non-existent implementation library '(null)\ws-2\32bit\vix.dll'

Feb 03 18:38:42.752: app-3892| config points to non-existent implementation library '(null)\server-1\32bit\vix.dll'

Feb 03 18:38:42.752: app-3892| Player installed version is 3.0.0

Feb 03 18:38:42.752: app-3892| No implementation found for service provider 4, apiVersion -1 installedVersion 3.0.0

Feb 03 18:38:42.752: app-3892| No Vix library found for provider 4 revision -1

Feb 03 18:38:42.752: app-3892| No implementation libraries loaded, cannot call 'VixJob_OnFinishAsynchOpWithHandle'

Build machine log file:

Feb 03 19:47:24.747: app-4260| Log for VixWrapper pid=4496 version=1 build=build-207905 option=Release

Feb 03 19:47:24.747: app-4260| The process is 32-bit.

Feb 03 19:47:24.747: app-4260| Host codepage=windows-1252 encoding=windows-1252

Feb 03 19:47:24.747: app-4260| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX
ws_server_esx-4\32bit\vix.dll'

Feb 03 19:47:24.748: app-4260| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX
ws_server_esx-4\32bit\vix.dll'

Feb 03 19:47:24.768: app-4260| config points to non-existent implementation library 'C:\Program Files (x86)\VMware\VMware VIX
ws_server_esx-4\32bit\vix.dll'

Feb 03 19:47:24.769: app-4260| passed in VIX_SERVICEPROVIDER_DEFAULT, computed hostType as 10

Feb 03 19:47:24.769: app-4260| Loading Vix implementation library C:\Program Files (x86)\VMware\VMware VIX
VIServer-2.0.0\32bit\vix.dll

Feb 03 19:47:25.276: app-4260| unable to load func VixVM_AddRollingTier from library C:\Program Files (x86)\VMware\VMware VIX
VIServer-2.0.0\32bit\vix.dll (127)

Feb 03 19:47:25.276: app-4260| unable to load func VixVM_RemoveRollingTier from library C:\Program Files (x86)\VMware\VMware VIX
VIServer-2.0.0\32bit\vix.dll (127)

Feb 03 19:47:25.276: app-4260| unable to load func VixVM_ListRollingTier from library C:\Program Files (x86)\VMware\VMware VIX
VIServer-2.0.0\32bit\vix.dll (127)

Feb 03 19:47:25.276: app-4260| unable to load func VixHost_OpenVM from library C:\Program Files (x86)\VMware\VMware VIX
VIServer-2.0.0\32bit\vix.dll (127)

Feb 03 19:47:29.021: app-4260| No such function 'VixHost_OpenVM' for version 4