OPERATIONAL DEFECT DATABASE
...
...
When attempting to start services on the Windows Server, it is resulting in Error 1053.
Upon encountering this issue, perform the following steps: Navigate to Start > Run > and type regeditNavigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ControlWith the control folder selected, right click in the pane on the right and select new DWORD ValueName the new DWORD: ServicesPipeTimeoutRight-click ServicesPipeTimeout, and then click ModifyClick Decimal, type '180000', and then click OKRestart the device The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager. By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service. If this does not work, please try the second solution below. 2. On Console server navigate to > AirWatch > AirWatch 9.x > Services > AW.Windowsupdates.dll > Right click Properties > Digital signatures > Digital Signatures details. You will notice error : A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. On finding this error we need to make sure the required Digital certs are present on the server with complete chain. Under MMC of console server > Go to Trusted root certificates> certificates and check if these certs are present: Digicert Assured ID Root CADigicert High Assurance EV Root CADigiCert Root CA In case of any of these certs are missing, we need to export them from the Lab server and import it to customer environment to trusted root certificates. Post this try restarting the services and it should work.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
