VMware vCenter Server not scanned in 11.1.1.3

[WuGe]

Since the update to v11.1.1.3 my VMware vCenter Server is not scanned anylonger.
It also no longer shows up as an asset.

Before the update all was OK. The vCenter and all scanned information was there.
We upgraded from v10.6.2.0
Scanning credentials are OK.
I have the vCenter IP with credentials as scanning target to scan it manually.
I can trigger the scan manually, the IP shows up in the scanning queue but seems not to be scanned because the vCenter server does not show up as asset and the widget stays empty.

Any ideas?

Update:
Logon with the given credentials works on the webclient/webpage of the vcenter.
LS calls the api and that logon runs into the error.

[Mister_Nobody]

LS 11121:

Exception(s) while trying to scan VCenter: Error during vCenter scanning: There is an error in the XML document.

[WuGe]

Lansweeper support confirmed there is a known issue with vcenter and esxi scanning and they are working on it.
They will release a fixed version soon.
LS support recommended to check the changelog page for updates.

https://www.lansweeper.com/changelog/

[Mister_Nobody]

Please scan vCenter via

"c:\Program Files (x86)\Lansweeper\Service\Lansweeper.TestTools.App.exe"

[WuGe]

Thanks.
That tool immediately throws an error when trying to scan the vcenter:

[WuGe]

I opened a support case now.

[WuGe]

When I start a manual scan of my vCenter Server my windows eventlog is filling with errors related to that job:

The first error in detail:

And I also have hundreds of .net errors that are lsagent related:

[Mister_Nobody]

Also Some Esxi-host are not scanning in my infrastructure

Vmware Error Unknown error

[WuGe]

@Mister_Nobody So it seems to be here too.
I do have them as asset but all the information / details are missing.

[AlbertD222]

Are you sure the Scan Service isn't crashing and failing to scan it at all?

I'm in the process of trying to figure out why our Scan Server constantly crashes after upgrading to 11 (I do have a ticket open, and they're looking into it). But from what I've found so far, mine crashes when I scan something by IP. but I'm still trying to trace it down. Not sure if its exactly due to it being by IP, or if its just non-windows items. As our Windows PC's & Servers pulled from AD seem to scan just fine. But Printers/Linux devices lock up the scan server service. 

[WuGe]

@AlbertD222 What do you mean in datail? My scaning service is up&running.
Your scanning service crashes and is stopped? 
Or do you mean windows eventlog entries?