Re: Error - Another version is already installed - VMware Technology Network VMTN

VMware Cloud Community

I am running Converter on Windows 7 ans trying to make a virtual machine of the current installation to upgrade to Windows 10.

Whenever I start to use the converter I get this error message "Unable to complete Converter agent installation on Dell-9020. Another version of this product is already installed.

I have looked around the machine and the only one I can find is the current installation.

Anyone any ideas. Thanks

17 Replies

Could you upload %tmp%\vm*.log files?

Is this the *.log you are looking for. farexec-service-log.txt

Created stop event 320

Client manager: Successfully spawned process, pid 12148

Client manager handling signaled event: Pipe disconnected.

Deleting service

Service helper received control [1]

Created stop event 320

Client manager: Successfully spawned process, pid 11344

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

Created stop event 320

Client manager: Successfully spawned process, pid 5984

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

Created stop event 320

Client manager: Successfully spawned process, pid 10060

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

Created stop event 320

Client manager: Successfully spawned process, pid 9896

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

Created stop event 320

Client manager: Successfully spawned process, pid 1308

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

Created stop event 320

Client manager: Successfully spawned process, pid 11344

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

Created stop event 320

Client manager: Successfully spawned process, pid 9780

Client manager handling signaled event: Pipe disconnected.

Service helper received control [1]

Deleting service

And... what to do with EXE file?

Not sure what you mean about the.exe file. I did not mean to attach that!

Installation logs are placed in %tmp% folder, they are named vm*.log, check them for error, if you can not detect one - upload them to investigate.

Run the following commands on the source machine to check for these services:

sc query vmware-converter-agent

sc query vstor2-mntapi20-shared

sc query bmdrvr

Is this the log file required...

Nope.

Have you execute commands from @Plamen?

These are the results from running the sc query items

vmware-converter-agent - this service is running

vstor2-mntapi30-shared - this service does not exist as an installed service

bmdvr - this service does not exist as an installed service

I have looked through the vm*.log files and there are a lot of Error : 0 entries and a few Incl NeedRebot Error :2 but nothing else.

Copies of the two log files are attached from TEMP directory

The vstor2 driver name is wrong, its vstor2-mntapi20-shared.

However, once the vmware-converter-agent is up and running - the other version is installed, deinstall and try again.

I have un-installed and re-installed the Converter and get the same error. Perhaps I will have to abandon Converter and use imaging instead. It must be easier!

Sorry for the typo. It is vstor2-mntapi20-shared

Now, let's clarify some things. Do you convert this local machine or a remote machine?

From your question

I am running Converter on Windows 7 ans trying to make a virtual machine of the current installation to upgrade to Windows 10.

it seems it is the local machine. However

Whenever I start to use the converter I get this error message "Unable to complete Converter agent installation on Dell-9020. Another version of this product is already installed.

implies a remote source machine (converting this local machine does not use the agent)

If you converter the machine where converter server is installed but select it by name/IP address (not as this local machine), Converter would still try to use the agent. However this is not necessary, just convert this local machine.

Assuming you convert a remote machine: if that's the case, then deinstall the agent in the source machine, get the agent installer from the machine where converter server is installed (%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\VMware-converter-agent.exe), copy it to the source machine, and run it. After that try the conversion.

HTH

Plamen

Hi

I had the same problem with converter 6.1 in Win 2008 R2 trying to convert a powered off Hyper-V guest to Workstation 11/12 format.

Both source and target were on the same computer.

To do this I did the following:

Select powered off hyper-v server
Specify loopback ip address 127.0.0.1 as server (actual ip address or machine name causes the converter wizard to attempt to install an agent which fails with another version error)
Specify machinename\administrator as user (another local user which is a member of local administrators group will get a permission denied error after pressing Next at source machine selection screen)
For the destination system, the target location has to be expressed as a UNC path ,for example, \\machinename\c$\targetdir

After the final Next and Finish, the conversion was successfully completed.

HTH.

Craig

Thank you Craig -

I can confirm (4 years later) that this also applies to a Hyper-V server running on Windows 10 2004 / same server location. I can also confirm that the local Administrator account can be invoked with both the machine hostname\{local admin} as well as {localhost|127.0.0.1}\{local admin}

One small addition that I needed in addition to your excellent steps - I also had to disable UAC in order to allow the Converter service to run.

Thanks again!

-Jon

I need help from experts.

I want to convert Hyper-V VMs to ova/ovf to upload in OneCloud.

I installed "VMware vCenter Converter Standalone 6.2 1" on the server where all the Hyper-V VMs running.

VM is currently powered down. When I launch Converter, showing the error message "Unable to complete converter agent installed on '127.0.0.1". Another version of this product is already installed."

I am unable to proceed further after the above message. I am trying to convert on the same machine, which means Source/Destination same.

Appreciate your help to fix this issue?

Thanks

-Nathan

It's 2024, I had the same issue with converting a Hyper-V VM from a 2019 host.

The converter is installed on the host & I got the same agent message when starting a conversion job.

The fix was to use localhost when connecting to the host - not the hostname or the IP address.

Once this was done it connected & I was able to configure the conversion job.

It appears that if you use the hostname or the IP address the task behaves as if you are accessing a remote host, detects itself essentially & throws the error.

This is with the current 6.6 converter