TRY NOW
book meeting
BACK TO KB LIST

Veeam vPower NFS Service fails to start

KB ID: 1094
Product: Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13
Published: 2011-07-20
Last Modified: 2025-12-09
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

This article documents troubleshooting steps to be taken if the Veeam vPower NFS Service fails to start.

Solution

Check Port Usage

Check if another process is locking one of ports used by the Veeam vPower NFS Service:

  1. Open an Administrative PowerShell Prompt
  2. Run the following command to check the ports used by Veeam vPower NFS Service.
    Shown in this example command is port 6161, but starting in Veeam Backup & Replication 13, if port 111 is locked by another process the service will now fail to start.
Get-Process -Id (Get-NetTCPConnection -LocalPort 6161).OwningProcess
  1. Review the output. If the port is in use by another process, stop that process and start the Veeam vPower NFS Service.

    The results of the command will either list a process, or an error will be displayed stating that no objects were associated with the port. "Get-NetTCPConnection : No MSFT_NetTCPConnection objects found with property 'LocalPort' equal to '6161'.  Verify the value of the property and retry."
Example of output when no processe is locking port 6161
Example of output when no processes is using port 6161.
Image shows powershell output of commands above, with the process name VeeamNFSSvc highlight as associated with port 6161
Example of output when Veeam vPower NFS Service is running correctly.
Alternatively, if another process is locking port 6161 and cannot be stopped, it is possible to change which port the vPower NFS Service uses. However, if another process is locking port 111, there is no way to change this, as that is the default NFS portmapper port.

More Information

Related Articles

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.