Automatic start service does not start p
Solved
randall
Posted messages
531
Registration date
Status
Member
Last intervention
-
randall Posted messages 531 Registration date Status Member Last intervention -
randall Posted messages 531 Registration date Status Member Last intervention -
Hello,
I just installed Diskeeper 2009, and I realized after a few days that the automatic defragmentation was not happening.
The reason is as follows: when I manually launch Diskeeper, I get the following message: "Diskeeper cannot connect to the service; it may be stopped."
Indeed, when looking at the list of services, the service is stopped even though it is set to automatic startup. I need to start it manually and do this every time I boot up the computer.
Where could this be coming from?
Thank you
I just installed Diskeeper 2009, and I realized after a few days that the automatic defragmentation was not happening.
The reason is as follows: when I manually launch Diskeeper, I get the following message: "Diskeeper cannot connect to the service; it may be stopped."
Indeed, when looking at the list of services, the service is stopped even though it is set to automatic startup. I need to start it manually and do this every time I boot up the computer.
Where could this be coming from?
Thank you
Configuration: Windows XP Pro Pack 2 Internet Explorer 7.0
6 answers
-
Hello,
Go to Start, Run, type: msconfig and OK. Startup tab, check: dkservice.exe, apply and OK. Restart and see what happens.
--
The human being is at his best when things are at their worst. -
Hello,
Thank you for the response, but the dk service is not present in ms config and it shouldn't be there because on a second computer everything works fine and the dk service file is not present.
In fact, even by double-clicking on dk service.exe, the service does not start; you have to go to administrative tools and services to start it. Furthermore, no errors appear in the event log.
The service it depends on is running, and I wonder what could be blocking it. -
Check if the firewall is blocking it.
--
The human being is at their best when things are at their worst. -
Hello,
The firewall does not block the service that is in the exceptions. Looking more closely, I have the following message in the event log.
"The dkservice has not started for the following reason, the service connection timeout is too long > 30000s".
In the Microsoft knowledge base, I found the solution that I am providing for those who might have the same problem:
To work around this issue, modify the Registry to increase the default timeout value for the service control manager. To increase this value to 60 seconds, proceed as follows:
Click Start, then Run, type regedit, and then click OK.
Locate the following Registry subkey and click on it:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
In the right pane, look for the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you need to create it. To do this, follow these steps:
In the Edit menu, point to New, and then click DWORD Value.
Type ServicesPipeTimeout, and then press ENTER.
Right-click on ServicesPipeTimeout, and then click Modify.
Click Decimal, type 60,000, and then click OK.
There you go, problem solved. -
Hello,
Actually, the error message was not on the Diskeeper line but on the service control manager line, so I didn't expect to find the error here.
Thank you and maybe see you soon. -
Strange! Earlier, you mentioned that there were no error messages in the event viewer and now there's a message for this error? The important thing is that it's resolved.
Have a good day.
--
The human being is at their best when things are at their worst.
