NetWorker Remote Exec Service does not start on Windows Cluster Nodes

Summary: NetWorker Remote Exec Service does not start on Windows Cluster Nodes

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

NetWorker Remote Exec Service does not start on Windows Cluster Nodes
  • NetWorker service will not start while node is active cluster node
  • Cluster has many disks
  • NetWorker service will start if the node is passive (and cluster-owned disks are NOT present on node)
  • Manually starting nsrexecd from the command-line works

Cause

Because of the extra disks associated with the cluster, NetWorker is unable to start within the Windows default 30 second timeout.

Resolution

Change the service start timeout to a greater value to allow for the extra time NetWorker needs to start.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
  3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type ServicesPipeTimeout, and then press ENTER.
  6. Right-click ServicesPipeTimeout, and then click Modify.
  7. Click Decimal, type 119000, and then click OK.
This value represents the time in milliseconds before a service times out. Any value greater than 120000 is ignored by the system.
  • Restart the computer.

Affected Products

NetWorker

Products

NetWorker
Article Properties
Article Number: 000064796
Article Type: Solution
Last Modified: 27 Sep 2023
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.