vSphere 6: Start Time Error (70034) When Adding ESXi Hosts

When adding an ESXi host to a cluster, you might see this error:

A general system error occured: Unable to get signed certificate for host <your host>. Error: Start Time Error (70034).

VCSA Error - Start Time Error (70034)

You are more likely to see this in a lab environment but may also see it in production, if you have just generated the certificate that replaces the VMware Certificate Authority (VMCA) root certificate, to make it an intermediate authority within your lab/organisation. I like to do that as pretty much the first thing after installation and before adding any ESXi hosts so that all compliant services from that point forward, get their certificate from the VMCA.

However according to this article, VMCA predates the ESXi certificates by 24 hours when adding them to the environment, to avoid time-synchronisation issues. If you’ve just generated VMCA’s own certificate, its time-stamp might become later in time than the generated ESXi certificates and hence the error. The suggested fix is to either wait 24 hours or add the hosts before replacing VMCA’s root certificate. If I have the choice, I prefer taking the first route as avoiding manual handling of certificates going forward is the whole point here.

Once it’s left for 24 hours, adding hosts works fine without any problems.

Hope this helps!

By | 2016-12-11T15:25:00+00:00 December 15th, 2015|vCenter, Virtualization, VMware, vSphere|0 Comments

About the Author:

Ather Beg is a technology and virtualisation blogger and is Chief Virtualogist at Virtualogists Ltd, which is a consultancy focusing on virtualised solutions. Ather has worked in IT for over 20 years and contributes his findings on this blog. In addition to holding several industry-related certifications, he has also been awarded vExpert status by VMware.

Leave a comment

%d bloggers like this: