Page 1 of 2
Client not started on Windows 10
Posted: Fri Mar 27, 2020 7:32 pm
by lanix
Hi,
I wanted to put the folding at home client on my professional computer which is a big machine but it does not work.
I install the client and when I start it, I do not have any icon in the windows bar (compared to my personnal computer on which it works).
I can see the process in the tasks manager but nothing else. the web control cannot access to the client. I tried to kill the process and start again in admin but same result.
Is there a way to have some logs or anyone have an idea on what is happening ?
Re: Client not started on Windows 10
Posted: Sat Mar 28, 2020 4:24 am
by Jesse_V
Hi and welcome to the forum.
I have a hunch on what's going on here. Do you have two users on that professional computer? For example, a regular and admin account. If so, try to log into the admin account and see if everything works on that account.
Re: Client not started on Windows 10
Posted: Sat Mar 28, 2020 5:24 pm
by lanix
Hi,
there can be multiple users on that computer but right now I am the only one log in on it and we are all admin on the system.
Any other idea ?
Re: Client not started on Windows 10
Posted: Sun Mar 29, 2020 8:28 pm
by Stel2112
There are logs in the program folder, \FAHClient\logs
By default this would be in C:\Program Files (x86)\FAHClient\logs
Maybe see if FAHControl.exe works? This is the "Advanced Control" exe.
Re: Client not started on Windows 10
Posted: Thu Apr 02, 2020 7:26 pm
by lanix
good clue to search for log, I did not find any in install folder but I found some in Appdata/roaming and there is an error on CUDA line but it seems correct since I do not have any GPU board on that computer.
I know that there are some works with CPU only and I have a big one to share. Is FAH application not running because I do not have graphical card ?
An extract of the log file :
Code: Select all
19:26:27:******************************** Build ********************************
19:26:27: Version: 7.5.1
19:26:27: Date: May 11 2018
19:26:27: Time: 13:06:32
19:26:27: Repository: Git
19:26:27: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
19:26:27: Branch: master
19:26:27: Compiler: Visual C++ 2008
19:26:27: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
19:26:27: Platform: win32 10
19:26:27: Bits: 32
19:26:27: Mode: Release
19:26:27:******************************* System ********************************
19:26:27: CPU: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
19:26:27: CPU ID: GenuineIntel Family 6 Model 158 Stepping 9
19:26:27: CPUs: 8
19:26:27: Memory: 63.89GiB
19:26:27: Free Memory: 60.13GiB
19:26:27: Threads: WINDOWS_THREADS
19:26:27: OS Version: 6.2
19:26:27: Has Battery: false
19:26:27: On Battery: false
19:26:27: UTC Offset: 1
19:26:27: PID: 8860
19:26:27: CWD: C:\Users\jduthil\AppData\Roaming\FAHClient
19:26:27: OS: Windows 10 Enterprise
19:26:27: OS Arch: AMD64
19:26:27: GPUs: 0
19:26:27: CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': Le
19:26:27: module spécifié est introuvable.
19:26:27:
19:26:27:OpenCL Device 0: Platform:0 Device:0 Bus:NA Slot:NA Compute:2.1 Driver:21.20
19:26:27:OpenCL Device 2: Platform:1 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:2117.13
19:26:27: Win32 Service: false
19:26:27:***********************************************************************
19:26:27:<config>
19:26:27: <!-- Folding Slots -->
19:26:27:</config>
19:26:27:Connecting to assign1.foldingathome.org:8080
the file ends with the last line above.
Re: Client not started on Windows 10
Posted: Fri Apr 03, 2020 12:01 am
by mandus
try this approach
viewtopic.php?f=106&t=33531
Re: Client not started on Windows 10
Posted: Fri Apr 03, 2020 12:42 pm
by lanix
Hi,
same thing, it does not work. I really think this is related to the fact that I do not have GPU.
Re: Client not started on Windows 10
Posted: Sat Apr 04, 2020 9:27 pm
by Stel2112
Have you tried installing FAH as a system service instead? That method does not use a GPU, it is made for CPU only. You might have better luck.
To install as system service, uninstall the client, then reinstall, goto custom install and select 'Start as a system service' when you get to that point.
Re: Client not started on Windows 10
Posted: Sat Apr 04, 2020 9:38 pm
by jxramos
Is there a way to verify whether or not a given install is setup as a service? What should I search for if I launch services.msc?
Re: Client not started on Windows 10
Posted: Sat Apr 04, 2020 9:42 pm
by bruce
Logs should NOT be in the system folder. That suggests that you're not using the shorcut that was delivered with the installer but rather that you're double-clicking on the *.exe.
Microsoft generally protects the system folder from files that are not put there by an official installer as a fairly reasonable defense against malware. Work files and logs, etc are supposed to be elsewhere. (Of coulrse if FAH is run by your Admin user, you can override that AV protection.
FAH's working files should be in C:\Users\<your username>l\AppData\Roaming\FAHClient
Re: Client not started on Windows 10
Posted: Sat Apr 04, 2020 9:55 pm
by PantherX
jxramos wrote:Is there a way to verify whether or not a given install is setup as a service?...
Welcome to the F@H Forum jxramos,
In the FAH log, under the system configuration, there is this line that is printed:
19:07:49: Win32 Service: false
That can tell you if you have installed as a service or not.
Re: Client not started on Windows 10
Posted: Sat Apr 04, 2020 10:05 pm
by Neil-B
With log finishing at connecting might this be a firewall issue
Re: Client not started on Windows 10
Posted: Sun Apr 05, 2020 4:40 pm
by lanix
Hi,
I tried to install it as a windows service as mentionned by Stel2112 but same result and same log file. Neil-B speak about firewall and that make sense, is there a way to confirm that ? I tried to copy paste the url of assign1.foldingathome.org in firefox and I can get to it. The log report that the port used is 8080, tell me if I am wrong but I think this is the standard one for http, so if I can see the page on my browser it should work, no ? or am I a noob in network ? (possible ^^)
Re: Client not started on Windows 10
Posted: Sun Apr 05, 2020 5:16 pm
by kostuek
Code: Select all
19:26:27:OpenCL Device 0: Platform:0 Device:0 Bus:NA Slot:NA Compute:2.1 Driver:21.20
19:26:27:OpenCL Device 2: Platform:1 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:2117.13
That looks strange. Maybe it is confused by two different platforms? What kind of a machine is this?
Re: Client not started on Windows 10
Posted: Sun Apr 05, 2020 5:39 pm
by lanix
kostuek wrote:
That looks strange. Maybe it is confused by two different platforms? What kind of a machine is this?
It is a Dell precision tower (do not remember the exact model name) with a i7-7700 at 3.6GHz for the CPU and 64Go of RAM