Services Won't Start

[jeremyking]

Having an issue with the Device Services server where the AirWatch services won't start. I get the error, "Windows could not start the *service name* service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion." 

I've tried adding the ServicesPipeTimeout entry to the registry, taking ownership of the Services folder, and making sure the server is fully updated. Nothing has helped. I'm on-prem, version 21.5.0.56 (2105).

Anyone else had this issue and managed to resolve it? 

[Noordan]

Hello,

Do you have any errors in event viewer and the CAPI2 logs?
I have seen this issue before if the signature of the service can't be validated against digicert crl-list. And if that is an issue, I think you should see errors about that in the CAPI2 logs.

You need access on port 80 to
http://crl3.digicert.com/
http://crl4.digicert.com/

[jeremyking]

No errors in the CAPI2 logs, just information logs. The AirWatch log under Applications and Services has plenty of errors. VMware support says it because port 1433 is blocked and the device server can't communicate with the SQL server. Now I have to try and figure out how a port just randomly closes itself.

[Noordan]

strange... a port are probably not just "closing itself" 😛 

you should be able to test int with powershell: test-netconnectio sqlserverip -port 1433

Have you found a solution on this?