Like the title says, when logging into vCenter 5.0 with the vSphere Web Client, I get an error that says its unable to connect to the vCenter Inventory Service.
The vCenter Inventory Service starts fine and is running as 'Local System', the same account used for all the other VMware related services.
I have done a bit of searching, but haven't found anyone that has my exact problem. Performance Overview works in vSphere Client, but searching the inventory does not.
Based on similar problems posted by others, I have looked at C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs\ds.log and found the following:
[2014-07-18 15:33:37,162 pool-14-thread-2 ERROR com.vmware.vim.dataservices.provider.VcProvider] com.vmware.vim.binding.vim.fault.InvalidLogin:inherited from com.vmware.vim.binding.vim.fault.Vimfault:inherited from com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.
[2014-07-18 15:33:37,162 pool-14-thread-2 WARN com.vmware.vim.query.server.provider.impl.ProvdermanagerServiceImpl] com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump@2e4ca30b
com.vmware.vim.query.server.store.exception.UnauthorizedException: not connected
at com.vmware.vim.query.server.provider.AbstractionAtamPullProviderBase.checkFeed(AbstractAtomPullProviderBase.java:89)
at com.vmware.vim.query.server.provider.impl.ProviderManagerServiceImpl$FeedPump.run(ProviderManagerServiceImpl.java:542)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask$run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.long.Thread.run(Thread.java:662)
That all repeats over and over. I've spent the last two days trying to figure this out, and I am out of ideas.
The log says that there is an incorrect username or password, but I am not sure where I can check and/or change it.