The issue occurs when an NSX object is created through the User Interface (UI) which contains invalid XML characters. When any client of the NSX Manager calls the NSX Manager API to access the object response, the API response contains the invalid XML character. Any processing on the invalid XML response on the client side fails due to the parse error.
This issue is resolved in VMware NSX for vSphere 6.3.7.
Workaround:
Do not use invalid xml character in the NSX object while creating any object from the User Interface (UI).
XML Payload of NSX-v API supports character set supported by XML 1.0 standard. As per the XML 1.0 standard, the supported character range is #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF].
Notes: