You are on page 1of 2

STATUS CODE 135: SAP Alternate client restores fail with a NetBackup Status Code 135 (client is not

validated to perform the requested operation), even though the No.Restrictions file is in use on a master server running Microsoft Windows.

Error
ERR - server exited with status 135: client is not validated to perform the requested operation

Solution
Overview: SAP Alternate client restores fail with a NetBackup Status Code 135 (client is not validated to perform the requested operation), even though the No.Restrictions file is in use on a master server running Microsoft Windows. Troubleshooting: On the Windows master server, see if Windows Explorer is set to hide file extensions for known file types. Log files: N/A Resolution: The No.Restrictions file (found in the <install_path>\veritas\netbackup\db\altnames\ directory) should not have any Windows file extension. If the No.Restrictions file is created in Notepad or a similar program, Windows automatically adds the .txt extension. If Windows Explorer is set to "Hide file extensions for known file types," the extension is not seen.

Either delete and recreate the No.Restrictions file without the extension, or remove the .txt extension. To recreate the No.Restrictions file without the extension: Open a command prompt and change to the <install_path>\veritas\netbackup\db\altnames directory. Then run the following commands: del No.Rest* (this deletes the existing file)
type null > No.Restrictions

(this creates the No.Restrictions file without any file

extensions) To view the hidden file extension and rename the existing No.Restrictions file: Launch Windows Explorer, and from the Tools menu, select Folder Options and then select the View tab (see Figure 1).

Figure 1

Make sure there is no check mark in the "Hide file extensions for known file types" option, as shown in Figure 1. Finally, browse the <install_path>\veritas\netbackup\db\altnames\ directory and rename the No.Restrictions file, to remove the .txt extension.

You might also like