Symptoms

After upgrading the NetWorker server, services do not start: Windows Operating SystemError (..\nsr\logs\daemon.raw): nsrctld NSR critical Shutdown due to error: Process NETWORKER_INSTALL_PATH\rabbitmq-server-3.2.4\bin\rabbitmq-server.bat exited in less than 10 seconds at startup: exit code 1 NetWorker: How to use nsr_render_log Uninstalling or Reinstalling does not resolve the issueRebooting the NetWorker server host does not resolve the issue

Cause

The Windows 8.3 short filename (SFN) is absent causing the rabbitq-server.bat to fail to run. This is an Operating System configuration issue. The non-8.3 paths cause the rabbitmq batchfile to fail: F:\>"F:\Program Files\EMC NetWorker\nsr\rabbitmq-server-3.2.4\bin\rabbitmq-server.bat" status Error spawning F:\EMC NetWorker\nsr\rabbitmq-server-3.2.4\erts-5.10.4\bin\epmd -daemon (error 0)

Resolution

8.3 file system support is required for NetWorker - it is considered unusual for it to be disabled. Confirm if 8.3 short filename (SFN) is enabled or disabled: Open an administrative command prompt on the NetWorker server. Switch to the drive NetWorker is installed on, for example: F:\ (This appears as an example throughout the remainder of the KB, ensure to use the drive or volume for your NetWorker installation) Run the fsutil command: F:\> fsutil 8dot3name query From the command output, determine the status, and ensure that the value is 0 or 2:The registry state is: 2 (Per volume setting - the default)0: Enables 8dot3 name creation for all volumes on the system1: Disables 8dot3 name creation for all volumes on the system2: Sets 8dot3 name creation on a per volume basis3: Disables 8dot3 name creation for all volumes except the system volume NOTE: For more information, see the following Microsoft article: https://technet.microsoft.com/en-us/library/ff621566(v=ws.11).aspx If the value is 1 or 3, unless some system requirement precludes it, run the following fsutil command to enable 8.3 SFN: F:\> fsutil 8dot3name set 0 Confirm if the directory structure for NetWorker contains 8.3 short filenames (SFN): Return to the administrative command prompt on the NetWorker server on the installation drive. From the root directory on the drive (in this example F:\), determine the traversal path to the rabbitmq-server.bat: F:\> dir /b /s rabbitmq-server.bat F:\> F:\Program Files\EMC NetWorker\nsr\rabbitmq-server-3.2.4\bin\rabbitmq-server.bat Check each traversal directory in turn for 8.3 SFNs through to the file: dir /x "{path_directory}" F:\> dir /x "Program Files" F:\> 09/10/2017 02:33 PM Program Files F:\> dir /x "Program Files\EMC NetWorker" F:\> 09/11/2017 03:43 PM EMCNET~1 EMC NetWorker In this example: EMC NetWorker has an 8.3 SFN EMCNET~1, but Program Files does not. NOTE: Files or folders which have eight characters or fewer, no spaces, and no extensions greater than three characters do not receive an SFN and can be ignored (that is nsr so forth). Files or folders which have spaces or　are greater than eight characters before first period or are greater than three characters after first period require SFNs. Enable and create a 8.3 short filename (SFN) for the NetWorker installation path: Shut down all running NetWorker server services, close any Windows Explorer windows or open other command lines, files or directory references anywhere in the NetWorker installation path: F:\> net stop nsrexecd /y For each folder missing 8.3 SFNs which requires one, create the SFN manually, by using the first six nonspace characters and a ~instance, e.g: F:\> fsutil file setshortname "Program Files" PROGRA~1 NOTE: If that SFN already exists, "Error: Cannot create a file when that file already exists." appears; try a different number (e.g ~2). When setting a 8.3 SFN on any directory ensure that there are no running processes, open prompts, file explorer windows in the path being renamed; otherwise an Access Denied error appears. F:\> fsutil file setshortname "Program Files" PROGRA~2 Restart the NetWorker server services: F:\ net start nsrd If NMC is installed on the same host: F:\ net start gstd WorkaroundTo avoid manually re-creating SFNs, Administrators may choose to create a Bootstrap backup of the NetWorker installation and reinstall after enabling SFN support on the intended file system. Keep in mind this would require deletion of the NetWorker installation following backup/uninstall: A file system copy of the installation is recommended while services are stopped. Newly created folders on an SFN-enabled file system receives SFNs by default. WARNING: Removal of NetWorker's installation root folder does not affect any parent it is installed into (such as Program Files), which would still need to be manually addressed, unless also deleted. This may not be practical if other applications are installed into the same folder. NetWorker can also be installed to a new root location outside of an affected structure. However - this in turn may lead to bootstrap recovery issues if a bootstrap is taken while NetWorker is installed to a different path than the existing, target recovery installation. This may provide an easier alternative for new installations.

Support Cases