Upgrade to RDM 2026.1.18.0 64-bit (JIT) Broke vCenter Synchronization
After upgrade to RDM v2026.1.18.0 64-bit (JIT) I'm no longer able to synchronize with any of our vCenters, receiving the following error:
System.ServiceModel.CommunicationException: Error in deserializing body of reply message for operation 'RetrieveProperties'. ---> System.InvalidOperationException: There is an error in XML document (7, 696). ---> System.InvalidOperationException: The specified type was not recognized: name='CustomFieldStringValue', namespace='urn:vim25', at <CustomFieldValue xmlns='urn:vim25'>. at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1521_CustomFieldValue(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1_Object(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1863_DynamicProperty(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1917_ObjectContent(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read2158_RetrievePropertiesResponse() at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer183.Deserialize(XmlSerializationReader reader) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) --- End of inner exception stack trace --- at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, XmlSerializer serializer, MessagePartDescription returnPart, MessagePartDescriptionCollection bodyParts, Object[] parameters, Boolean isRequest) --- End of inner exception stack trace --- at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, XmlSerializer serializer, MessagePartDescription returnPart, MessagePartDescriptionCollection bodyParts, Object[] parameters, Boolean isRequest) at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest) at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest) at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters) at System.ServiceModel.Dispatcher.ProxyOperationRuntime.AfterReply(ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.<CreateGenericTask>b__0(IAsyncResult asyncResult) --- End of stack trace from previous location --- at Devolutions.VMwareManagement.InventoryNavigator.RetrieveObjectContents(String[][] typeinfo, Boolean recurse, ManagedObjectReference startFolder) at Devolutions.VMwareManagement.InventoryNavigator.SearchManagedEntities(String[][] typeinfo, Boolean recurse, Boolean withPath) at Devolutions.VMwareManagement.VMwareSoapClient.GetVMList(Boolean withPath)
Recommended Answer
Hello,
We have a fix for this issue which should be available starting from the upcoming RDM 2026.1.20.0.
Please let us know if the issue persists after updating to the above-mentioned version once it is released.
Best Regards,
Michaël Beaudin
Hi jlapchuk,
Thanks for reaching out us!
This looks like a VMware SOAP inventory deserialization failure during RetrieveProperties: vCenter is returning a CustomFieldValue typed as CustomFieldStringValue, and the VMware SOAP client used by RDM 2026.1.18 isn’t recognizing that type, so synchronization fails while parsing the inventory.
Workaround to try first
If Legacy or Experimental works, that strongly suggests a compatibility issue specific to the Default API path with your vCenter version.
To confirm, please share:
Thanks in advance!
Best regards,
Eduard Sepulveda Lopez
Following, as all ours broke and so removed consoles till I could resolve.
They either out right failed when using Default or legacy or returned "no new machines found" when using experimental.
I did have a filter on, if removed it would add in every vm it found but would also duplicate the entry. I would have 4 consoles per VM.
Thanks
Iain
Version 2026.1.20.0 64-bit
Data Source SQL
This issue is also happening for us. Exact same results as Iain.
I have no filters or any special configurations on this. Just default.
How can we get this resolved?
Hi jlapchuk,
Thanks for reaching out us!
This looks like a VMware SOAP inventory deserialization failure during RetrieveProperties: vCenter is returning a CustomFieldValue typed as CustomFieldStringValue, and the VMware SOAP client used by RDM 2026.1.18 isn’t recognizing that type, so synchronization fails while parsing the inventory.
Workaround to try first
If Legacy or Experimental works, that strongly suggests a compatibility issue specific to the Default API path with your vCenter version.
To confirm, please share:
Thanks in advance!
Best regards,
@Eduard Sepúlveda López
None of the legacy or experimental APIs work for us, same as everyone else on this thread. This appears to be a bug introduced with this latest version.
Hi jlapchuk, Iain and jphelps,
Thank you for the detailed report and the error details.
We have confirmed this as a bug, and our development team is actively working on a fix. To make sure we can track progress centrally and notify you as soon as a corrected build is available, this thread has been moved to the Bug Reports section. Updates will be posted there as soon as we have them.
Thanks for your cooperation and understanding.
Best regards,
Eduard Sepulveda Lopez
Hello,
We have a fix for this issue which should be available starting from the upcoming RDM 2026.1.20.0.
Please let us know if the issue persists after updating to the above-mentioned version once it is released.
Best Regards,
Michaël Beaudin