This is caused by a fault in the VMware tools, see FB13667. The debug log will show the following:
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write7_MethodFault(String n, String ns, MethodFault o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write8_LocalizedMethodFault(String n, String ns, LocalizedMethodFault o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write9_Item(String n, String ns, ToolsConfigInfoToolsLastInstallInfo o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write10_ToolsConfigInfo(String n, String ns, ToolsConfigInfo o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write37_VirtualMachineConfigInfo(String n, String ns, VirtualMachineConfigInfo o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write143_VMwareXMLStorage50(String n, String ns, VMwareXMLStorage50 o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterVMwareXMLStorage50.Write144_VMwareXMLStorage50(Object o)