VMware Cloud Community
kapplah
Enthusiast
Enthusiast

[BUG?] Problems with "umlaute" in Ressource Pools after Upgrade of VC to 2.5

Hi there,

seems that there is a small bug in Virtual Center when using german umlaute (mutated vowels) in ressource pools after our Upgrade to Virtual Center 2.5

Especially when I try to deploy a virtual machine from a template to a ressource pool with those umlaute in it's name, I'll get a error after 90% "communication timed out with remote host". Even renaming the Ressource Pool is not possible, ending with the same error. The Umlaut is also not displayed correctly in Virtual Center - instead of the Umlaut a suqare is displayed. Also the Virtual machines below this Ressource Pool are not visible for VC.

As a workaround, I connected with the OLD VI Client the the Server directly, created new Ressource Pools without Umlaute and moved the VMs the them. Although I was able to rename the invalid named Ressource Pools, the new name was NOT mirrored when connecting to the Virtual Center 2.5

Any Ideas how to remove that (now) orphaned Ressource Pools?

Is there any mismatch in Character Encoding (VC / SQLDB)?

regards,

Alex

0 Kudos
0 Replies