Hi,
It looks like some validation issue with the VC certificate.
Removing of the VRMS database won't help. Perhaps neither VC re-installation.
There is a Managed IP Address runtime setting of VC. The "vCenter Server Address:" in VRMS VAMI Configuration page should be populated with this value by default. That might matter, but only if IP address is filled in "vCenter Server Address:" - there would need to be a subject alternative name in the VC certificate for that IP address (it should be there for the default VC self-signed certificates).