Stumbled upon this error also. Seems to be a known issue (KB Article) with vSphere 5.1 + Web Client.
Best regards,
Bjoern
