I have created a task on vCenter 6.0.
Task name as is shown different on vSphere web client 6.0 and vSphere client 6.0.
Task name is shown correctly on vSphere client 6.0.
But on vSphere web client 6.0 there is additional '.label' attached at end of task name.
Attached web client screenshot for reference.
Spent some time on the phone today working this issue, the problem we found was tied to a Netapp plugin that we installed in our environment. The plugin version was 6.2.1P1D1, which was where the problem ended up being. 6.2.1P1D1 is the service version for the plugin and the Virtual center JAR only interprets service versions on plugins that contain numbers, it cannot interpret letters. When it tries to process the Netapp plugin it fails and never loads the rest of the files containing the appropriate lables. The hope is that this will be resolved to read both numbers and letters in the future. Hope this helps or at least points you in the right direction.
Thank you! This put me on the right track and the issue is now resolved.
For anybody else that has this issue, I checked Administration > Client Plugins but there was only the default plugins and a plugin for VCops.
I disabled that but it made no difference so I then ran through this KB article:
Using this I found several old NetBackup plugins that were registered under /mob but not showing up in the vSphere client.
Once I followed the instructions for un-registering them and rebooted the VCSA the problem was resolved.
I updated today the VCSA from 6.5 to 6.5 Update 1 and I have now the "task description label" Problem. 😞
Installed NetApp VSC Plugin Version: 6.2.1P1
Is there still another solution instead of disabling the NetApp plugin?
This is unfortunately not an option for us.
I had the same issue with Task names and Host Profile settings showing the full ".label" names after an upgrade from 6.0U2 to 6.5.
I logged a support case and VMware gave me an updated "vim-services-6.1.0.jar" file to patch the web client (Flex Client).
The update file worked fine and the issue was resolved.