If you log in to a non-English version of the vSphere Client, an error message might appear in the Recent Task list.

After you deploy vRealize Infrastructure Navigator on a non-English version of the vSphere Web Client, the Recent Task list might display a label not found error message. This error message also appears in the Task Console of the vSphere Web Client.

This issue is caused by a VPX i18nfilter limitation on the language fallback mechanism.

For vCenter Server on a Windows machine:

a

Create a dummy locale folder under the directory C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale in the vCenter Server. For example, C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale\de, C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale\fr, C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale\ja, C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale\zh_CN, or C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale\ko.

b

Copy all the English resource files under C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vadm\locale\en to the locale folders that you have created.

vCenter Server loads the strings correctly by using the dummy resource files.

For vCenter Server on a Linux machine:

a

Create a dummy locale folder under the directory /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale in the vCenter Server. For example, /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale/de, /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale/fr, /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale/ja, /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale/zh_CN, or /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale/ko.

b

Copy all the English resource files under /usr/lib/vmware-vpx/extensions/com.vmware.vadm/locale/en to the locale folder that you have created.

vCenter Server loads the strings correctly by using the dummy resource files.