1

Our VSphere web client is playing funny games. If I log in the domain account it’s fine (Sometimes) Sometimes it shows no VM’s anywhere. If I log in with administrator@vsphere.local all sorts of errors appears such as:

"Could not connect to one or more vCenter Server systems: https://vcenterservername:443/sdk "

“Unable to create the managed object for - urn:vmomi:TaskManager:TaskManager:6260E46C-0714-4649-A34E-29B6BC46FDEB.”

Logging in with VSphere client on the server it didn’t log in at first then did a few mins later. VMWare support have been pretty rubbish and simply saw it logged in find on the client and said it was working and just to send them logs.

We are running 5.5 at the moment and have 3 hosts.

Anyone have any ideas, this is getting pretty critical as we have no backups that can run as Veeam also fails to connect to Vcenter randomly.

5 Spice ups
2

Look at just updating the VCenter - it is a VCSA, right? If not, it should be.

I have found that for the time it takes to mess with obscure settings in the older VCSA versions, I could spin up a new one with the latest version, and point the hosts (and Veeam) to it.

This should help - https://www.altaro.com/vmware/3-ways-update-vcenter-server-appliance-6-5/

1 Spice up
3

5.5 is EOL in September, you want to migrate/upgrade this.

But as simple as this sounds, have you rebooted vcentre, if not, why not?

1 Spice up
4

Its VCenter on a windows VM. Yes it has been rebooted as has Veeam. We are upgrading in 3 weeks and migrating to VCSA but would like backups solved first.

5

Have you called VMware support on this?

6

This was due to a Windows update. Uninstalling from the server solved the issue. VMWare support were not much help on this.