Can't add VM back to vCenter inventory

[sh4yne]

Hello. I found file for a VM on one of our datastores. I don't see the VM anywhere in Virtual Center. When I try to add it to the inventory, I get the following error:

"A virtual machine or a template having the samename is already registered. Server error: The specified key, nam, or identifier already exists."

The vmware.log file has these entries

May 21 07:53:06.529: vmx| SOCKET 1 client closed connection
May 21 07:53:06.529: vmx| vmdbPipe_Streams: Couldn't read

Is there something I'm missing? Is there a way to add the VM back to my inventory? Thank you in advance for the advice and help!

Shayne

[Troy_Clavell]

you are sure you've verified that the object name does not exist in vCenter. What you can do is highlight the Hosts&Clusters View then go to the right and side where it says:

Name, State, Host or Guest OS contains. Do a search through your inventory for the name in question.

[kjb007]

If you rename a vm in the vCenter inventory, then that name will not match what you see in the datastore browser. What you see in datastore browser is the original name of the vm. If you download the vmx file to your desktop, and open it up with notepad, there will be a field within it called displayName. That is the current name that will show up in your inventory, and which should already be there by the error message you received.

-KjB

VMware vExpert

[sh4yne]

Both answers taught me new tricks, so thank you both. I downloaded the file using KjB's suggestion. I copied the display name and searched for it using Troy's suggestion.

However, I could not find the names of the files or the displayNames from the VMX files in Virtual Center.

I actually have two VMs in this predicament, and can not find names for either one.

[Troy_Clavell · Accepted solution]

have you tried to restart your vCenter Server Service?

[msemon1]

When you rename your VM's do you change the file names or do a cold migration so the VM and file names match?

Mike

[MauroBonder]

try using command line

vmware-cmd

Options:

Connection Options:

-H <host> specifies an alternative host (if set, -U and -P must als o be set)

-O <port> specifies an alternative port

-U <username> specifies a user

-P <password> specifies a password

General Options:

-h More detailed help.

-q Quiet. Minimal output

-v Verbose.

Server Operations:

/usr/bin/vmware-cmd -l

/usr/bin/vmware-cmd -s register <config_file_path>

/usr/bin/vmware-cmd -s unregister <config_file_path>

/usr/bin/vmware-cmd -s getresource <variable>

/usr/bin/vmware-cmd -s setresource <variable> <value>

VM Operations:

/usr/bin/vmware-cmd <cfg> getconnectedusers

/usr/bin/vmware-cmd <cfg> getstate

/usr/bin/vmware-cmd <cfg> start <powerop_mode>

/usr/bin/vmware-cmd <cfg> stop <powerop_mode>

/usr/bin/vmware-cmd <cfg> reset <powerop_mode>

/usr/bin/vmware-cmd <cfg> suspend <powerop_mode>

/usr/bin/vmware-cmd <cfg> setconfig <variable> <value>

/usr/bin/vmware-cmd <cfg> getconfig <variable>

/usr/bin/vmware-cmd <cfg> setguestinfo <variable> <value>

/usr/bin/vmware-cmd <cfg> getguestinfo <variable>

/usr/bin/vmware-cmd <cfg> getproductinfo <prodinfo>

/usr/bin/vmware-cmd <cfg> connectdevice <device_name>

/usr/bin/vmware-cmd <cfg> disconnectdevice <device_name>

/usr/bin/vmware-cmd <cfg> getconfigfile

/usr/bin/vmware-cmd <cfg> getheartbeat

/usr/bin/vmware-cmd <cfg> getuptime

/usr/bin/vmware-cmd <cfg> gettoolslastactive

/usr/bin/vmware-cmd <cfg> getresource <variable>

/usr/bin/vmware-cmd <cfg> setresource <variable> <value>

/usr/bin/vmware-cmd <cfg> hassnapshot

/usr/bin/vmware-cmd <cfg> createsnapshot <name> <description> <quiesce> <mem ory>

/usr/bin/vmware-cmd <cfg> revertsnapshot

/usr/bin/vmware-cmd <cfg> removesnapshots

/usr/bin/vmware-cmd <cfg> answer

[sh4yne]

It was restarted for another reason. The day ofter the restart, I moved the VM's files to another host, and I was able to add it to inventory.