• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Service Failed to start

mike400hp

n00b
Joined
Feb 14, 2005
Messages
48
My work Windows XP workstation rebooted itself last night due to an automatic update that required a reboot. I have since set the automatic updates to just download and prompt for me to install them manually. Now the problem is that I checked the event log it shows that the F@H failed to start. Do I have to be logged in under my account before the service will start?

event1.jpg

event2.jpg
 
Can you please post the path to where you currently have the FAH502-console.exe placed? It appears from the two screenshots you've posted that you had it setup as a service at two different locations, c:\ and c:\program files\folding@home... If you've moved this file, Windows will no longer be able to find it, and it will give the errors shown.

 
Where are your FAH client files located? That service entry is pointing to C:\. I think you may have it in C:\FAH\. Is this the case?

 
Yup... just need a little more info...

If you're running two console clients.... you need them in two different directories, i.e F@H 1 and F@H 2.... Then run the setup... and set them to start as a service.... reboot and they should both start on their own...


Keep on Folding!!

 
I'm running it from C:\FAH

services.jpg


Ahhh... That's the problem. I ran the setup a few times when I was first getting it configured. How do I remove those services?
 
You'll need to reconfigure the client using the -configonly switch to re-set it up as a service at the current path. As I noted earlier, the errors you showed us tell that it was in different locations when it registerd as a service. Once you've set it up, you can then go to the services tab and just fire it up.

Depending on your comfort level with registry editing, you can get rid of the other two service entries by navigating to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
and removing the entries for those F@H services.

 
Thanks, I removed those keys and of course made a back before I did that. Better to be safe than sorry.
 
Back
Top