VMware Cloud Community
cfriedline
Contributor
Contributor
Jump to solution

The specified key, name, or identifier already exists; convert fails

All,

When doing a conversion of a VM, I get the following message immediately after the attempt to create the destination VM. In the tasks window of VC, I see The specified key, name, or identifier already exists. In the VMware Converter window, I see "n. Pelase wait for that import to finish before opening this source again". This occured after a previous conversion attempt failed (too many virtual connections).

How do I convert this VM now? I've rebooted, uninstalled/reinstalled (deleted install folder) the Converter Agent. This server is Windows 2000 SP4, and I'm running the converter on the VM to be converted from a UNC path.

Thanks,

Chris

Reply
0 Kudos
1 Solution

Accepted Solutions
gautam
Expert
Expert
Jump to solution

Everybody's favourite error message, here's the workaround: -

1) On the source host, open regedit

2) Navigate to HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM

3) Export the key for backup-archive-restore purposes

4) Delete CcmPort3 thru CcmPort9

5) Retry the migration

View solution in original post

Reply
0 Kudos
11 Replies
cfriedline
Contributor
Contributor
Jump to solution

Looking in the vmware-client.log file, I see these messages:

\[2007-02-01 15:54:10.716 'P2V' 4176 error] \[task,295] Task failed: P2VError IMPORT_SOURCE_ALREADY_OPENED()

\[2007-02-01 15:54:10.716 'P2V' 4176 verbose] \[task,339] Transition from InProgress to Failure requested.

Anyone have any ideas?

Thanks,

Chris

Reply
0 Kudos
Jasemccarty
Immortal
Immortal
Jump to solution

Have you tried importing it with a different destination name?

Jase McCarty - @jasemccarty
cfriedline
Contributor
Contributor
Jump to solution

I haven't. I didn't want to get stuck in a situation where my names didn't match with no way to fix it. I'll give it a whirl and see what happens.

Reply
0 Kudos
cfriedline
Contributor
Contributor
Jump to solution

OK, I tried that. Now getting this error message: "Number of virtual devices exceeds the maximum for a given controller."

Reply
0 Kudos
gautam
Expert
Expert
Jump to solution

Everybody's favourite error message, here's the workaround: -

1) On the source host, open regedit

2) Navigate to HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM

3) Export the key for backup-archive-restore purposes

4) Delete CcmPort3 thru CcmPort9

5) Retry the migration

Reply
0 Kudos
cfriedline
Contributor
Contributor
Jump to solution

Looks like that was it. Not sure how I missed it on a search. Thanks!

Reply
0 Kudos
cfriedline
Contributor
Contributor
Jump to solution

Any reason you know why I would be getting the error in the Subject? I'm hoping that I can rename the VM in VirtualCenter after the migration. Thoughts?

Reply
0 Kudos
Jasemccarty
Immortal
Immortal
Jump to solution

Looks like Converter needs to "drop off" Com3 through Com9... Automatically.

Jase McCarty - @jasemccarty
Reply
0 Kudos
chouse
Enthusiast
Enthusiast
Jump to solution

I got that message all the time during beta testing - the VM would fail to create and the beta wouldn't back it out so it was stuck there with no way to remove it.

Migrate with a new destination name and then try renaming it once it's all finished.

Reply
0 Kudos
joeperry25
Contributor
Contributor
Jump to solution

Looks like this is not just for COM ports but for any serial port outside the COM1 and COM2 range. I migrated a dell 2650 that had a RAC Card in it and it failed repeatedly in about 20 seconds until I removed the RAC card from the mentioned registry location. Tks for the help guys

Reply
0 Kudos
VMwareman85
Contributor
Contributor
Jump to solution

I had the same issue, and I was able to correct it through HKLM...But, were you able to identify why this error" The specified key, name, or identifier already exists" kept coming up. Is there something specific that needs to be deleted? I'm trying to find where this instance would be, I can't find it on the Datastore that I'm using.

Reply
0 Kudos