Centrify

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  >
article

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

Auditing and Monitoring Service ,  

12 April,16 at 11:11 AM

Problem:

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.
===========

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

Resolution:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  3. In the right pane, locate the ServicesPipeTimeout entry. 
Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:​
  1. Type ServicesPipeTimeout, and then press ENTER.
  2. On the Edit menu, point to New, and then click DWORD Value
  • Right-click ServicesPipeTimeout, and then click Modify.
  • Click Decimal, type 180000, and then click OK.
    This value represents the time in milliseconds before a service times out.
  • Restart the computer.
 
For more information, please refer to the Microsoft KB article (provided as a courtesy):

Related Articles

 No related Articles