In this situation, typically the vCenter database will contain a record that suggests that a dvPort with the number of '###' in "in use". This is why vCenter is issuing that error message.
However, when you look at the output from the command "esxcfg-vswitch -l" on the ESXi host, the "in use" associated with that dvPort "###" may contain "0" (which means it is not in use).
The dvPort "###" could be associated with a vmkernel interface. The vmkernel interface could be one associated with Management, vMotion, VSAN or other services.
Also, the dvPort "###" could be associated with a virtual machine that has a snapshot that has not been consolidated.
Also, the dvPort "###" could be associated with a virtual machine template.
The best way to remedy this, will depend on which type of network connection is associated with the dvPort "###" in the error message.
If you determine that:
Then you can follow the procedure below:
In all other cases, we would suggest that you open a Support Case by following the process in Creating and managing Broadcom support cases.