Ako kada pokrenete svoje Windows računalo, usluga^(Service) se ne pokrene, a ID događaja 7000^{(ID 7000)} , 7009 ili 7011 su prijavljeni u Windows Event Log , tada vam ovaj post može pomoći. U ovom ćemo postu ponuditi rješenje za rješavanje ovog problema.

Usluga se ne pokreće – ID događaja 7000^{(– Event ID 7000)} , 7009, 7011^(Service)

Događaji pogreške mogu se pojaviti u zapisniku aplikacije^{(Application)} u sljedećem formatu:

Događaj 1^{(Event 1)}

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000

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

Događaj 2^{(Event 2)}

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011

Description:
Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.

Događaj 3^{(Event 3)}

Event Type: Error
Source: Service Control Manager
Event ID: 7009
Task Category: None

A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect.

Da biste zaobišli ovaj problem, morate modificirati Registry kako biste povećali zadanu vrijednost vremenskog ograničenja na 60 sekundi^{(60 seconds)} za upravitelja kontrole usluge.

Upravitelj kontrole usluge čeka vrijeme koje je navedeno u unosu ServicesPipeTimeout prije evidentiranja događaja 7000, 7011 ili 7009. Usluge^(Services) koje ovise o usluzi Windows Trace Session Manager mogu zahtijevati više od 60 sekundi za pokretanje. Stoga povećajte vrijednost ServicesPipeTimeout  na odgovarajući način kako biste svim ovisnim uslugama dali dovoljno vremena za početak.

Povezano čitanje^{(Related read)} : Ispravite pogrešku ID-a događaja 7031 ili 7034^{(Event ID 7031 or 7034)} kada se korisnik odjavi.

Budući da se radi o operaciji registra, prvo biste trebali napraviti sigurnosnu kopiju registra^{(back up the registry)} ili stvoriti točku vraćanja sustava u slučaju da postupak pođe po zlu. Nakon što ste poduzeli potrebne mjere opreza, možete nastaviti na sljedeći način.

1. Pritisnite tipku Windows + R. U dijaloškom okviru  Pokreni upišite ^(Run)regedit i pritisnite Enter.

2. Pronađite^(Locate) i zatim kliknite sljedeći potključ registra:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. U desnom oknu pronađite  unos ServicesPipeTimeout .

Ako unos ServicesPipeTimeout ne postoji, morate ga kreirati . Da biste to učinili, slijedite ove korake:

• Kliknite izbornik Uredi^(Edit) ili prazan prostor u desnom oknu, a zatim kliknite Novo^(New) > DWORD (32-bitna) vrijednost^{(DWORD (32-bit) Value)} .
• Upišite ServicesPipeTimeout , a zatim pritisnite Enter.

4. Desnom tipkom miša kliknite ServicesPipeTimeout , a zatim kliknite  Izmijeni^{(Modify )} da biste uredili njegova svojstva.

5. Odaberite radio gumb za Decimal pod Base , zatim upišite 60000 pod Vrijednosti^(Value) podataka. Ova vrijednost predstavlja vrijeme u milisekundama prije isteka usluge.

6. Kliknite OK .

7. Ponovno pokrenite računalo kako bi promjene stupile na snagu.

Vaš problem bi trebao biti riješen.
^{(Your issue should be resolved.)}

Pročitajte više^{(Read more)} : Rješavanje problema Windows usluge se neće pokrenuti^{(Troubleshoot Windows Services will not start)} .

A Service does not start error with Event ID 7000, 7009, 7011

If when you start your Windows computer, a Ѕervice dоes not start, and event ID 7000, 7009 or 7011 are logged in the Windows Εvent Log, then this post may be able to help you. In this post, we will offer a workaround to address this iѕsue.

A Service does not start – Event ID 7000, 7009, 7011

The error events may appear in the Application log in the following format:

Event 1

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000

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

Event 2

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011

Description:
Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.

Event 3

Event Type: Error
Source: Service Control Manager
Event ID: 7009
Task Category: None

A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect.

To work around this problem, you need to modify the Registry to increase the default time-out value to 60 seconds for the service control manager.

The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000, 7011 or 7009. Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start.

Related read: Fix Event ID 7031 or 7034 error when a user logs off.

Since this is a registry operation, you should first back up the registry or create a system restore point in case the procedure goes wrong. Once you have taken the necessary precautionary measure, you can then proceed as follows.

1. Press Windows key + R. In the Run dialog, type regedit, and hit Enter.

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. In the right pane, locate the ServicesPipeTimeout entry.

If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:

• Click the Edit menu or an empty space in the right pane, then click New > DWORD (32-bit) Value.
• Type ServicesPipeTimeout, and then hit Enter.

4. Right-click ServicesPipeTimeout, and then click Modify to edit its Properties.

5. Select the radio button for Decimal under Base, then type 60000 under Value data. This value represents the time in milliseconds before a service times out.

6. Click OK.

7. Restart the computer for the changes to take effect.

Your issue should be resolved.

Read more: Troubleshoot Windows Services will not start.

Related posts

• Popravite ID događaja Upravitelja kontrole usluge 7001 u sustavu Windows 11/10

• Pogreška ID-a događaja 158 - Dodjela identičnih GUID-ova diska u sustavu Windows 10

• Popravi pogrešku ID-a događaja 7031 ili 7034 kada se korisnik odjavi s računala sa sustavom Windows 10

• Kako popraviti pogrešku ESENT ID događaja 642 u sustavu Windows 11/10

• ID događaja 307 i 304 s kodom pogreške 0x801c001d na Windows 11/10

• Popravite ID događaja 14 i 17 - neuspjeh TPM naredbe u sustavu Windows 10

• Kako omogućiti ili onemogućiti IP Helper Service u sustavu Windows 10

• Popravi Arhiva je ili u nepoznatom formatu ili je oštećena pogreška

• Upravljajte Windows uslugom iz sistemske trake pomoću ServiceTray-a

• Popravi naziv događaja problema BEX64 u sustavu Windows 10

• Usluga platforme povezanih uređaja je prekinuta

• Usluga ovisnosti ili grupa nije se uspjela pokrenuti u sustavu Windows 11/10

• Pronađite ovisnosti Windows usluge | Automatski ponovno pokrenite usluge

• Windows nije mogao pokrenuti uslugu, pogreška 0x80070005, pristup je odbijen

• ID događaja 1098: Pogreška 0xCAA5001C, operacija posrednika tokena nije uspjela

• Kako uključiti bilježenje otklanjanja pogrešaka u usluzi Windows Time Service

• ID događaja 219 kada je uređaj priključen; Učitavanje upravljačkog programa WUDFRD nije uspjelo

• Popravi pogrešku ID-a događaja 454 - problemi s izvedbom korisničkog profila u sustavu Windows 10

• Postavke dopuštenja specifične za aplikaciju ne odobravaju lokalnu aktivaciju

• Kako mogu omogućiti uslugu dodirne tipkovnice i ploče za rukopis?