Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-2740: Why is the collector service not starting? (Event ID 7000 and 7009)

Centrify DirectAudit ,  

12 April,16 at 11:11 AM

Applies to: All versions of Centrify DirectDirect 2.x or higher

When starting the collector service, it ends up with the following error messages and Event ID 7000 and 7009:

The DirectAudit 2012 Collector service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

This is similar to the issue as described in:
The collector service takes longer than the timeout value when issuing connection to SQL server.

1. In Registry Editor, locate and right-click on the following registry subkey: 
2. In Control, in the right pane of Registry Editor, right-click and choose "New" then "DWORD". 
3. Replace New Value #1 with ServicesPipeTimeout and then press ENTER.
4. Right-click the newly created ServicesPipeTimeout registry entry and click Modify.
5. In the Value data text box, type 180000, and click OK
** Note TimeoutPeriod is a placeholder for the value of the time-out (in milliseconds) set for the service. 
For example, to set the time-out period to 24 hours (86400000 milliseconds), enter 86400000.  
6. Restart the computer for the Service Control Manager to apply this change.

** Restart of computer is required **


Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

No related Articles