- This topic has 3 replies, 2 voices, and was last updated 8 years, 2 months ago by
.
-
Posts
-
The NoMachine Server service dies e few seconds after start. OS is Win7 SP1. NoMachine version is nomachine_5.1.9_7. Before this version was installed (and rebooted), the old version was uninstalled and rebooted. For testing purposes, the firewall is disabled. Netstat does not show any conflict on port 4000. I have another Win 7 machine with the same NoMachine version and OS without problems on the same network albeit different hardware and software installed.
Any ideas?
Thomas
Hi, we’ve sent you a debug package to allow us to extract more details about what could be provoking this issue. Please check your email and the instructions within.
This issue seems to be the same as one already reported: https://www.nomachine.com/forums/topic/clean-install-service-doesnt-start-win-10
Newly created nxserver processes can’t load all necessary dependencies. This can be verified using Process Monitor.
Follow these instructions:
1. Download and install Process Monitor from this site:
https://technet.microsoft.com/pl-pl/sysinternals/processmonitor2. Shut down or kill all NoMachine processes.
3. Run Process Monitor as Administrator.
4. In Process Monitor Filter window:
– Expand ‘Column’ drop down list (default value is ‘Architecture’), change the value to ‘Command Line’.
– Expand ‘Relation’ drop down list (default value ‘is’), change the value to ‘contains’.
– Type ‘daemon’ in the ‘Value’ field.
– Set ‘Action’ field to ‘Include’.
This should create rule: ‘Command Line contains daemon than Include’.– Click on ‘Add’, ‘Apply’ and ‘Ok’.
5. In top bar of Process Monitor check ‘Show Registry Activity’, ‘Show File System Activity’, ‘Show Network Activity’,
‘Show Process and Thread Activity’ and ‘Show Profiling Events’ icons.6. Run ‘nxserver –startup’ from command line.
7. After 30 seconds click on ‘Save’ icon in Process Monitor top bar.
Save file using ‘Native Process Monitor Format’. Send us produced event file (to forum[at]nomachine[dot]comWe received the logs but they were not helpful in our investigations to understand why this was happening on your Windows 7. We were unable to reproduce on any of our installations. All we can suggest is that you upgrade the NoMachine software, if you haven’t done so already, and see if the problem continues.
This topic was marked as solved, you can't post.