While trying to troubleshoot another problem, we tried Refreshing vCloud to vCenter which includes registering/updating the extension. This is when we hit a beauty we’d never seen before:
Alright, calm down. Probably something with the network, right? And if it’s not the network then it’s probably DNS. Right? Wrong.
I dug around in the vCenter MOB and found the vCloud Director extension. As expected it already had a “vCloud Director-1” named extension. What I found odd was the last heartbeat time was back in 2013. Interestingly enough the last version recorded was also v5.1.2. I say interestingly because we are running v8.10.1 for SP.
Jumping into our test environment, I performed a Refresh of our test vCloud instance to vCenter and lo and behold it happened there too! I couldn’t find anything in the vCloud logs reporting the why behind this failure, but I needed to get this running and quick, too.
Knowing that the vCloud DB stores its own references to the vCenter MOB, and that vCloud would try to register itself as vCloud Director-1 again, I theorised that we could remove the existing extension and perform another Refresh without causing any issues.
So, that’s what I did right in the test environment. It went without a hitch. Rolled the same change out in production and it went beautifully.
If you’re getting this error, I’d suggest taking a backup of your vCenter server/DB and removing the existing vCloud Director extension.
Removing the extension (from KB1025360):
- In a web browser, navigate to http://vCenter_Server_name_or_IP/mob.
Where vCenter_Server_name_or_IP/mob is the name of your vCenter Server or its IP address.
- Click Content.
- Click ExtensionManager.
- Select and copy the name of the plug-in you want to remove from the list of values under Properties. For a list of default plug-ins, see the Additional Information section of this article.
- Click UnregisterExtension. A new window appears.
- Paste the key of the plug-in and click Invoke Method. This removes the plug-in and results in void.
- Close the window.
- Refresh the Managed Object Type:ManagedObjectReference:ExtensionManager window to verify that the plug-in is removed successfully
Now go back to vCloud and perform a Refresh against your vCenter server. You should be back in action now!