This is a known issue affecting the Cloud Director 10.3.x versions.
If you cannot migrate to a Cloud Director 10.4 version, please open a Support Request.
The workaround involves Database Manipulation which should always be done in collaboration with VMware Technical Support.