STATUS CODE 67: Attempts to initiate hot catalog backups fail with NetBackup Status Code 67 (client backup failed to read the file list).

Problem

STATUS CODE 67: Attempts to initiate hot catalog backups fail with NetBackup Status Code 67 (client backup failed to read the file list).

Solution

Overview:  Attempts to initiate hot catalog backups fail with NetBackup Status Code 67 (client backup failed to read the file list).  

When a hot catalog backup is initiated, it backs up the stage information without error, but on the second child job it fails with Status 67.

Troubleshooting:
Review the files in the <install_path>\veritas\netbackup\db\images directory and see if there are any unusual characters

Log files:  
In the bpbrm log file on the media server, the following line is observed:
<32> bpbrm main: from client svcacibu1: FTL - file list read failed (22)

The bpbkar log file on the client server has the following:
10:35:56.755 AM: [3400.4744] <16> V_CatBackupWin::V_StartDBBackupSession: ERR - db_startBackup failed, unable to obtain initial catalog file list: err: 22
10:35:56.755 AM: [3400.4744] <2> tar_base::V_vTarMsgW: FTL - file list read failed (22)

7:25:09.686 AM: [3660.4576] <16> V_CatBackupWin::V_StartDBBackupSession: ERR - db_startBackup failed, unable to obtain initial catalog file list: err: 22
7:25:09.686 AM: [3660.4576] <2> tar_base::V_vTarMsgW: FTL - file list read failed (22)
7:25:09.686 AM: [3660.4576] <4> backup_create: INF - NetBackup Temp Directory: 'G:\Program Files\VERITAS\\NetBackup\Temp'
7:25:09.686 AM: [3660.4576] <4> tar_base::V_StopKeepaliveThread: INF - The Keepalive Thread has Exited. Wait Reason:WAIT_UNKNOWN
7:25:09.686 AM: [3660.4576] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 67: client backup failed to read the file list

Resolution:
A review of the files in the <install_path>\veritas\netbackup\db\images directory determined there were corrupt files.  One of the file names was <par>R<box>lck, in which <par> was the paragraph symbol, and <box> was a box.  The only letters were the "R" and "lck".  There was no way to move, copy, rename, or FTP these corrupt files.  Once these corrupt files were removed,  backups were successful.