While following the documentation, the following errors are seen when trying to run Centrify's ZPA using a service account which is allowed to 'log in as a service':
"Failed to start service. The service did not respond to the start or control request in a timely fashion."
There does not seem to be any logs related to this failure, what could be the cause?
In a very locked down environment, queries to AD may take longer than normal to respond thus affecting the startup the ZPA services. It has nothing to do with delegation.
Below are the steps to extend the timeout:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
- Type ServicesPipeTimeout, and then press ENTER.
- On the Edit menu, point to New, and then click DWORD Value
- Right-click ServicesPipeTimeout, and then click Modify.
- Click Decimal, type 180000, and then click OK.
This value represents the time in milliseconds before a service times out.
- Restart the computer.
For more information, please refer to the Microsoft KB article (provided as a courtesy):