2 Answers
- Newest
- Most votes
- Most comments
1
If Yes, this happens only when the service won’t start with in allocated 30seconds for each service and it’s through time out error and move on to next service/ To fix this, you need to increase the timeout value from 30 seconds to 60 seconds in Windows Registry. Here is the Windows KB article# https://learn.microsoft.com/en-US/troubleshoot/windows-server/system-management-components/service-not-start-events-7000-7011-time-out-error
answered 2 years ago
0
Assuming that it’s a time out errors that you see in windows logs every time CloudWatch agent is not running!
answered 2 years ago
Relevant content
asked 4 years ago
asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
