Hi Terrance,
I hope I have solution for this - but be careful and check if it fits also for you...
I was just able to resolve same error message at one of our customers (got me to some troubles with NSX installation - apparently as a consequence of this problem you won't be able to fully deploy NSX on TN, it won't connect with controller part of the manager, but that is another story).
The problem is with HPE bundled software - check the ESXi host for installed vibs:
esxcli software vib list | grep ams
You should see results:
amscli, amsd (and amsdhelper probably)
Problem is with amsd and amscli. I'm not sure which one should be gone for you as I was tshooting this on Synergy and the wrong one there is amscli (it is not even in the offline bundles for Synergy, not sure how it got on the ESXi), but my guess would be that it will be amscli also.
The module amsd already "has" amscli (amscli is extension of esxcli, the amsd has it too) and if you check folder /usr/lib/vmware/esxcli/ext/ you will see there 2 XMLs, which are basically the same structure/content wise with just different names (amsd-smadrev.xml and smad_rev.xml) and are causing the problems.
Anyway for me to resolve the problem, I have just removed the vib:
esxcli software vib remove -n amscli
Hope it helps,
J.
