We are facing an issue with vsphere client the last 2 days. An error message appears suddenly while connected in vcenter server 4.1
vSphere Client error : An internal error occurred in vSphere Client Details An item with the same key has already been added
It happens in two completely diferrent VMware isolated clusters.
By clicking the close button there is no interuption but actually we need to figure if it is something wrong or just a false allarm.
Hello,
Moved to the vCenter forum.
Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]
Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]
I am also recieving this error - seems to appear when I have about 5-6 console windows open and switching beween them, does not seem to be a big issue, but is a pain.
Mark
same messag here
it does not affect the environment but it bothers
same problem here..
Moving between consoles, make the error window jump
Until now it happened to us only with vSphere client on windows xp workstation
We have vCenter 4.1
thanks
I have the same problem. I'm having 3 console windows open. Running 4.1 update1
I'm receiving the same error message after migrating an ESX 3.5 cluster to a vCenter 4.1 host. Has anyone found a resolution to this?
Users are still reporting this with vSphere Client 4.1.0 build 345043 connected to ESXi 4.1 update 1 build 381591 servers.
Any update on this issue? The KB simply says it's a known issue.
I'm also experiencing the same problem with the 4.1 U1 client build 345043 with ESXi 4.1 build 260247 systems.
KB Article: 1035639
For those who have 4.1 U1 seems that the problem is resolved in new version 4.1 U2
the funny think is that if you moved to vS5 what should you do? sonyvadakel downgrade...
I found this VMware KB: 2030029
But it says to disable the VUM plug-in. So I tried the following:
I removed my windows profile on the machine I was using the vSphere client and re-created it.
That solved the issue.