The NetBackup Messaging Broker service fails to start on Windows if the 8dot3 short file name setting is disabled

Problem

The NetBackup Messaging Broker service supports core primary server functions including backups, restores, alerts and notifications. On a Windows system, the NetBackup Messaging Broker service fails to start if the 8dot3 short file name setting is disabled on the volume where NetBackup is installed.

To check if installation root folder has the 8dot3 file name setting enabled, run the following command from your folder:
>dir /x

Example: The Program Files directory has the 8dot3 file name setting enabled, therefore the short name PROGRA~1 is generated.
But it differs for the ‘not8 Dot3’ directory.

C:\>dir /x
The volume in drive C has no label.
The Volume Serial Number is FE21-2F8E

Directory of C:\
-5.6.3
12/06/2019  02:24 PM    <DIR>                                   not8 Dot3
12/02/2019  06:35 AM    <DIR>          PROGRA~1     Program Files
12/02/2019  10:44 AM    <DIR>          PROGRA~2     Program Files (x86)

Cause

The NetBackup Messaging Broker service fails to start if the 8dot3 short file name setting is disabled on the volume where NetBackup is installed.

Solution

• Enable 8dot3 name file setting for the NetBackup installation root folder using the fsutil command.
  Refer to the following article:
  Fsutil 8dot3name

•  If the problem persists, please reach out to Veritas Technical Support.

Additionally, similar startup issues have been observed when a rogue file or folder named 'program' exists on the root of the drive letter on which NetBackup is installed.  
See article 100050881 for more details.