Loading...
Loading...
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
Because of the extra disks associated with the cluster, NetWorker is unable to start within the Windows default 30 second timeout.
Change the service start timeout to a greater value to allow for the extra time NetWorker needs to start. Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control On the Edit menu, point to New, and then click DWORD Value. Type ServicesPipeTimeout, and then press ENTER. Right-click ServicesPipeTimeout, and then click Modify. 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.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.