VMware {code} Community
reisenhoferf
Contributor
Contributor

[VIX API 1.10.1] Problems while connecting to vmware player 3.1.1

Hello,

Some days ago a new version of VMWARE Player (3.1.1) was released.

We are using VIX API to start vmware images. The code is .

This code works fine with vmware player 3.1. But with the new version 3.1.1 we are getting a connection error saying, that the specified version was not found.

Any idea whether the new version of vmware player is not longer supported by VIX API? Or if yes: What are the changes?

Thanks for a hint.

Best Regards

Frank R.

serviceProviderVM = VixCOM.Constants.VIX_SERVICEPROVIDER_VMWARE_PLAYER

' Connect VMware Workstation or VMware Server.

job = libc.Connect(VixCOM.Constants.VIX_API_VERSION, serviceProviderVM, Nothing, 0, Nothing, Nothing, 0, Nothing, Nothing)

' Wait for results of connecting to virtual machine host.

vmErr = job.Wait(propertyIDS, results)

job.WaitWithoutResults()

If libc.ErrorIndicatesFailure(vmErr) Then

Err.Raise(VIX_ERROR_NUM, Nothing, libc.GetErrorText(vmErr, Nothing))

Else

Start: 08-17-2010 16:28:59

Error during connecting to C:\VirtualMachines\Win7_64Bit\NONPERSISTENT_Windows7x64.vmx

Description: The specified version was not found

Error during starting virtual machine.

Tags (7)
Reply
0 Kudos
2 Replies
admin
Immortal
Immortal

Hi Frank R.,

I am sorry about this. This a due to a limitation of how VIX detects compatibility between the installed version of VIX and the installed product. We default to assuming that new products are not backwards compatible with "older" VIX releases (we rely on some code that is not very tolerant of changes).

As a work around, you will have to modify a text file in your VIX installation directory (usually C:\Program Files\VMware\VMware VIX\).

Find the file named "vixwrapper-config.txt", and add the following line at the end:

player   13  vmdb  3.1.1 Workstation-7.1.0

Sorry again about the inconvenience.

Reply
0 Kudos
reisenhoferf
Contributor
Contributor

Thanks for your fast reply. The workaround solved the issue.

Reply
0 Kudos