vSphere 6.0 U1

[alexander_d]

After applying this hotfix we're facing an issue with vsphere web client...
We have Veeam server installed on vCenter Server.
After applying a hotfix VMware vSphere Web Client fails to start with multiple errors in C:\ProgramData\VMware\vCenterServer\logs\rhttpproxy\rhttpproxy.log
2015-XX-XXTXX:XX:41.994+02:00 warning rhttpproxy[04472] [Originator@6876 sub=Proxy Req 00155] Connection to localhost : 9090 failed with error class Vmacore::SystemException(No connection could be made because the target machine actively refused it).
with root cause in
C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\eventlog.log
we see an error message:
[2015-XX-XXTXX:XX:34.849+02:00] [ERROR] system-artifacts <TC0011E> Failed to start Tomcat. Port 443 is in use.
All other web services running on this host (PCS and SSO) functioning correctly. Veaam is functioning as well.
Currently we're investigating this issue with VMware (SR15774446210).
Please report if anyone had similar issue with vcenter server and veeam server installed on the same machine.

[veremin]

Just to clarify - are you talking about VMware fix or Veeam Update 3?

[jamerson]

Hi guys
i have installed the patch U3 on one of our customers Veeam server, however after trying to backup Win 10 it still says unsupported OS.
any suggestions why ?
installed the patch on another server of a different customer trying to backup Win 10 now.

[jamerson]

people with the same issue. I've rebooted the server and it fixed .

[rreed]

Built a new 6.0 vCenter appliance, updated a couple hosts to 6.0 U1a, migrated a few test VM's over to the hosts, sure enough backups failed (something about couldn't find the .vmx or file was locked). Applied Veeam Update 3, bounced Veeam server, it came up and said it needed to update all my proxies, let it, rebooted all Veeam/proxies once more for good measure, retried my failed backups succeeded normally w/o issue. Back on track now.

Well done Veeam guys, many thanks. Now about that MICROSOFT##SSEE database warning that doesn't go away despite being in the database exclusions...

[adrien.herve]

Hi guys,

I'm still facing this issue ERR |SSL error, code: [336151568].error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure with my ESXi host after the workaround vmauthd.ssl.noSSLv3 = "FALSE" for authd service was applied in my config file.
I'm using ESXi 6.0 Update 1b build 3380124 and Veeam 8.0.0.2029 (I can't upgrade to Veeam 8 update 3 right now).

Any ideas why it's not working? Maybe this KB https://kb.vmware.com/kb/2121021 is not applicable on ESXi 6.0 U1b?

[foggy]

Adrien, please contact technical support. They could verify the issue and provide you with the hotfix for Veeam B&R Update 2.

[adrien.herve]

Thank you but I think I'll plan the upgrade in the last stable v8 build which is fully compatible with vSphere 6 U1 though. The solution for re-enable SSLv3 on ESXi hosts has a lower impact on our production but it may take a while to “fix” all the hosts and potentially enable a security breach. A workaround is definitely not a way to do something sustainable.

I hope the last Veeam build will not have side-effects on our central backup servers. I’ll upgrade soon from 8.0.0.2029 to 8.0.0.2084 and see what's happen.

[foggy]

I hope the last Veeam build will not have side-effects on our central backup servers.

Do you mean you have several Veeam B&R servers in your environment? Then, if you're going to upgrade just one of them, make sure they do not use the same servers as proxy/repository, since components having different versions cannot coexist.

[adrien.herve]

Yes I have two backup servers for some reasons, especially for guest file restore otherwise I need to mount VMDKs accross datacenters which is a pain.
They don't share proxies or repositories so I think everything is safe.

[foggy]

Yes I have two backup servers for some reasons, especially for guest file restore otherwise I need to mount VMDKs accross datacenters which is a pain.

Then consider upgrading to v9, which addresses this pain with the help of the mount server.