Editing the Source "Network Profile" in the HCX User Interface fails and throws the following error:
NSX-T config was not found for VC uuid <REDACTED_UUID>
In the app.log you will be similar error messages:
2026-03-23 19:49:09.275 UTC [NSXService_SvcThread-134, Ent: HybridityAdmin, , TxId: ] INFO c.v.v.h.s.n.NsxTInventorySyncJob- Processed Segments from Networks 2 :[]
2026-03-23 19:49:09.721 UTC [NSXService_SvcThread-134, Ent: HybridityAdmin, , TxId: ] ERROR c.v.v.h.s.n.NsxTInventorySyncJob- Failed to update NsxT Inventory
org.codehaus.jettison.json.JSONException: JSONObject["vcuuid"] not found.
at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:426)
at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:562)
at com.vmware.hybridity.adapters.nsxtransformers.NsxConfigurationBuilder.getVcUuidForNsxtUuid(NsxConfigurationBuilder.java:159)
at com.vmware.vchs.hybridity.service.nsxservice.NsxTInventorySyncJob.fetchNsxtEntities(NsxTInventorySyncJob.java:353)
at com.vmware.vchs.hybridity.service.nsxservice.NsxTInventorySyncJob.run(NsxTInventorySyncJob.java:115)
at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
2026-03-23 19:49:09.862 UTC [NSXService_SvcThread-134, Ent: HybridityAdmin, , TxId:] INFO c.v.v.h.s.n.NSXInventoryService- Cancelling NsxTInventorySyncJob for NSX-T UUID:##-##-###-## and jobId:##-##-###-## on signal from saas-adapter
VMware HCX
This error occurs when an NSX Manager is incorrectly registered with the source/on-premises HCX Manager in the Appliance Management interface, while no actual NSX Manager is installed or utilized in the associated source environment. When editing the Network Profile, HCX attempts to validate against this stale or incorrect NSX configuration and fails.
Log in to the HCX Appliance Management interface at https://<HCX-Manager-IP>:9443 using admin credentials.
Navigate to the Configuration tab and locate the NSX section.
Click Delete to remove the incorrectly registered NSX-T Manager configuration.
Navigate to the Service/Troubleshooting section and Restart the Web Service and Application Service to clear the old configuration cache.
Log in to the standard HCX User Interface at https://<HCX-Manager-IP>.
Navigate to Infrastructure > Interconnect > Network Profiles.
Select the affected Network Profile, click Edit, and then click OK to re-save and validate the profile without needing to modify internal fields.
Maintenance Step: If WAN Optimization (WANOPT) was utilized and impacted by the previous misconfiguration, schedule a maintenance window (changes to the Interconnect will cause a brief service interruption). Edit the associated Compute Profile to remove WANOPT, then update the Service Mesh to push the changes to the Interconnect (IX) appliances.