Failed to start NFS service , the endpoint is a duplicate.

[hvbuel]

Its driving me nuts, I cant get the vpower NFS service started.
This windows server was upgraded from V7 to V8.
The vpower NFS server is set to automaticly start, but it does not start.
A manual restart failes, reinstalling the NFS service also fails.
Microsoft NFS service is NOT running, so I dont get why vPower NFS wont run.

Help appreciated.....

[foggy]

Hi Harald, please include the support case ID for this issue, and we will take a look.
Also, please avoid posting log snippets, as requested when you click New Topic.
Thanks!

[Vitaliy S.]

What does Windows Event log show when you try to start the service?

[hvbuel]

I can only find a message in the SYSTEM event log.
It says : The Veeam vPower NFS Service service entered the stopped state.
No mention of starting the vPower NFS service or why it fails to stay started.
The popup on the screen says that the vPower NFS service has started but also stopped immediately, this sometimes happens when the service is not being used, according to said pop-up.

[tdewin]

Please make sure you have a call opened so that support can look at your case

Last time I had this error, another process was using the port so you might look at custom software you have installed

[hvbuel]

Support case id : 00871895

The Svc.VeeamNFS.log file suggests that port 6161 is in use : Failed to register TCP/IP RPC endpoint. Port: [6161]
But for the life of me I can not find any other process using that port.

[tdewin]

use

Code: Select all

netstat -a -b -n > c:\logports.txt

to find out the ports connected to the process. You must run the shell with Administrator rights. Open the file with notepad and look for 6161. Notice that the process name is under the tcp/ip connection info (due to indentation it looks like it is first the process name and then the tcp/ip connection info)

[hvbuel]

The netstat commando did not reveal a conflicting process, however we did find one using the resource manager on this windows machine.
Snarecore.exe was running using port 6161, it was installed by our security officer to support our IDS/IPS device.
After stopping the Snarecore.exe process vPower was able to start successfully.
We will reconfigure the IDS/IPS software to use other ports.
Mystery solved, thank you all for your input.

[veremin]

Otherwise, you can change the vPower NFS by going to the settings of given repository -> vPower NFS -> Ports and specifying there the desired value. Thanks.