Aspect Posted November 22, 2017 Share Posted November 22, 2017 As my monitored machines are updating to the new Windows 10, the agent simply will not start automatically.. Any idea why? Link to comment Share on other sites More sharing options...
yclaf Posted November 22, 2017 Share Posted November 22, 2017 Change the start service "automatically" with "automatically late" (Sorry for my English) Link to comment Share on other sites More sharing options...
Aspect Posted November 22, 2017 Author Share Posted November 22, 2017 Tried that (Automatic (Delay)) on 2 machines. No affect. Link to comment Share on other sites More sharing options...
Staff Chris Posted November 22, 2017 Staff Share Posted November 22, 2017 Hi, At first please have a look into the Windows event log, to find out why the Pulseway service fails to start (look for the entry from Service ControlManager), if the error is that service did not respond to start or control request in timely manner, then the first thing that you can try is to configure the Pulseway service start as Automatic(Delayed Start) and/or recovery options. But If that doesn't help, then you can try to increase the startup timeout by running built in script 'Increase Windows Service Timeout at Startup' (You can adjust the timeout interval. In this script it is set to 60000ms [60 seconds]). Our customers get the best results if the timeout interval is set to 90000 (90 seconds). Paul 1 Link to comment Share on other sites More sharing options...
SEHale Posted January 12, 2018 Share Posted January 12, 2018 On 11/22/2017 at 12:32 PM, Chris said: Hi, At first please have a look into the Windows event log, to find out why the Pulseway service fails to start (look for the entry from Service ControlManager), if the error is that service did not respond to start or control request in timely manner, then the first thing that you can try is to configure the Pulseway service start as Automatic(Delayed Start) and/or recovery options. But If that doesn't help, then you can try to increase the startup timeout by running built in script 'Increase Windows Service Timeout at Startup' (You can adjust the timeout interval. In this script it is set to 60000ms [60 seconds]). Our customers get the best results if the timeout interval is set to 90000 (90 seconds). I am having the same problem - new install today. I set the service to start as Automatic (Delayed Start) but that didn't help. Not sure where to look for the script to change timeout interval. Thanks. Link to comment Share on other sites More sharing options...
SEHale Posted January 13, 2018 Share Posted January 13, 2018 Disregard - I found the script editor on the web page, changed the timeout interval to 90000 and all is working great! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now