Answer

PROBLEM

• A timeout was reached (60000 milliseconds) while waiting for the GFI EventsManager service to connect
• Error 1053: The service did not respond to the start or control request in a timely fashion

ENVIRONMENT

• GFI EventsManager

SOLUTION

1. Increase the default service timeout settings as described in the following Microsoft knowledgebase article: http://support.microsoft.com/kb/941990
2. Ensure that your GFI EventsManager Licensing page is not reporting that you are over your license count on either your Server licenses or Workstation licenses, as this may cause this issue
3. If the Microsoft Knowledge Base article does not solve the issue, it may be necessary to create an exception for the user that the GFI EventsManager service runs as by disabling CRL (Certificate revocation list) checking for that user only, using Microsoft Setreg. Setreg can be downloaded from the following link: http://ftp.gfisoftware.com/support/ESM/Tools/setreg.zip
   1. Perform the following procedure to disable CRL checking for the GFI EventsManager user:
      1. Login to the GFI EventsManager server using the GFI EventsManager service user
      2. Open command prompt
      3. Change the directory to the directory storing setreg.exe
      4. Run the following command:  setreg.exe 3 FALSE
         • Note: The setting above can be reverted by running the following command:  setreg.exe 3 TRUE
      • ​Further information about Microsoft Setreg can be found at: http://msdn.microsoft.com/en-us/library/7zaf80x7(VS.80).aspx

CAUSE

The GFI EventsManager executables are digitally signed by default. When trying to start the service, the application must download the Certificate Revocation List to authenticate. If the download fails due to network connectivity or security reasons the service will fail to start by timing out.