NetBackup for Microsoft SQL Server backup fails with Status Code 5452

Problem

NetBackup for SQL Server backup fails with status code: 5452

Error Message

The script cannot be accessed for execution.

Jun 18, 2018 1:57:31 PM - Error bpbrm (pid=4376) from client sql-12: ERR - The script <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch> cannot be accessed. Confirm the script on client <sql-12> can be accessed and is in an authorized local location.
Jun 18, 2018 1:57:31 PM - Error bpbrm (pid=4376) from client sql-12: ERR - bphdb exit status = 5452: The script cannot be accessed.
Jun 18, 2018 1:57:31 PM - Info bphdb (pid=5620) done. status: 5452: The script cannot be accessed.

Cause

This problem can arise if the service account specified in the NetBackup Client Service and NetBackup Legacy Network Service is not a member of the local Administrators group, or if the batch file has been inadvertently named using a *.txt extension rather than a *.bch extension.  For example, when saving the batch file in notepad, the *.txt extension may be added by default.  This can be determined by examining the file name via command line rather than via File Explorer.

C:\Program Files\Veritas\NetBackup\DbExt\MsSql>dir
Volume in drive C has no label.
Volume Serial Number is 3E01-F252

Directory of C:\Program Files\Veritas\NetBackup\DbExt\MsSql

06/18/2018  01:55 PM    <DIR>          .
06/18/2018  01:55 PM    <DIR>          ..
02/03/2018  01:26 PM               403 bkup.txt

Solution

Ensure the service account is a member of the client's local Administrators group. 

Rename the file such that it has an extension of *.bch.  Using the above example, we can use the Windows rename command (ren) or it could be renamed via file explorer.  To rename via command line:

ren bkup.txt bkup.bch

The dir command will now show the correct *.bch extension:

C:\Program Files\Veritas\NetBackup\DbExt\MsSql>dir
Volume in drive C has no label.
Volume Serial Number is 3E01-F252

Directory of C:\Program Files\Veritas\NetBackup\DbExt\MsSql

06/18/2018  01:55 PM    <DIR>          .
06/18/2018  01:55 PM    <DIR>          ..
02/03/2018  01:26 PM               403 bkup.bch

About authorized local locations:

See the following article for information on registering authorized locations used by a NetBackup database script-based policy, which can also resolve this error:

https://www.veritas.com/support/en_US/article.100039639