vCenter 5.5 u2b running on windows 2012 r2. Noticed the VMware vCenter Inventory Service took 18 minutes to start vs the normal 3 minutes.
C:ProgramDataVMwareInfrastructureInventory ServiceLogsds.log was filled with “Processing unresolved entities”.
Ex.
Line 1245: [2016-05-22 12:02:44,414 pool-14-thread-1 INFO com.vmware.vim.vcauthorization.impl.provider.InMemoryAuthCache] Processing unresolved entities xxxxxx
Install ADSI Edit.
Open ADSI edit. Right click on ADSI Edit, Connect to…
Name – View ADAM Database
Connection Point – dc=virtualcenter,dc=vmware,dc=int
Computer – The FQDN of the Win 2012 VC VM you are RDP’ed to.
Expand OU=Instances
Right click on the first CN=xxxx and click Properties
Scroll down to “vmw-vc-URL” and edit the URL to the correct FQDN of the VC. An old one may appear if you did a fresh VC 5.5 install on a new VM using the existing external SQL database.
Reboot the VC VM.
After the reboot, reset the Inventory Service Database. Make sure to backup tags and note SRM will need to be repaired. https://kb.vmware.com/kb/2042200
If you are running VC 5.5 U3 or higher you can avoid nuking the tags and SRM. https://kb.vmware.com/kb/2133427