I had an issue when using update manager to scan a host and it would fail with a “Check log for errors blah blah blah”. The errors are never useful. After investigating and checking the log, I found the following entry:
2015-06-02T20:57:30.312-07:00 [00504 info ‘VcIntegrity’] Error on logout (ignored): vim.fault.NotAuthenticated
When researching the issue, I came across a best practices guide that basically pointed out the error. So as a general best practice, verify on your hosts, on the configuration tab, under DNS and Routing, that you have filled in all the fields. I had missed the Search Domain field on that particular host which was causing the scan to fail.
The fields with the blue boxes will cause the Update Manager scan failure as well as cause other issues with DNS on the host. Just another one of things to check!
As always, leave questions or suggestions in the comments.
I had to redeploy a vCenter Server Appliance recently and got an error when opening vCenter: sysimage.fault.SSLCertificateError.
This is caused by the certificate on the vCenter Server changing. This causes the Upgrade Manager needing to be re-registered with the vCenter Server. Luckily, VMware provides a utility to do just that. Go to your vCenter Upgrade Manager Server (The appliance does not include this, so it will typically be installed on a separate Windows Server).
Go to “C:\Program Files (x86)\VMware\Infrastructure\Update Manager” and open the file “VMwareUpdateManagerUtility”.
Next, enter the credentials for your vCenter Server and hit Login.
Once the window opens, you’ll want to click “Re-register to vCenter Server”. This brings up another login screen. You can use the same credentials you did to open the utility here as well.
Finally click apply and you will receive a notification that you need to restart the VMware vSphere Update Manager in order for the settings to take affect.
Restart the service and open the vSphere Client again. The error will be gone and you’ll be able to use Update Manager again.