NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

In the VERITAS NetBackup (tm) 5.0 for UNIX and Windows Troubleshooting Guide, the recommended action for Status code 135 is incorrect.

The manual incorrectly shows the same recommended action for both status code 135 and 136. The correct recommended action for a status 135 is: Retry the operation as a root user (administrator on Windows) on the master server. Also see status code 131.
TECH31835 | 2005-01-29
Technical Solutions | CMS-XML

NetBackup for VMware credential validation fails: VMware credential validation failed. (Status code: 135)

2 bpVMutil main: unable to get server credentials 2 bpVMutil main: EXIT STATUS 135 : client is not validated to perform the requested operation
TECH130686 | 2014-08-21
Technical Solutions | CMS-XML

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.

ERR - server exited with status 135 : client is not validated to perform the requested operation
TECH28924 | 2013-10-23
Technical Solutions | CMS-XML

Media Manager status code 135

Media Manager status code 135
HOWTO90997 | 2013-10-02
How To | CMS-XML

NetBackup status code: 135

NetBackup status code : 135
HOWTO90556 | 2013-10-02
How To | CMS-XML

When using NetBackup Database extension for Oracle, a restore fails with RMAN error ora-27029 and NetBackup status code: 135.

15:29:08 [26493] 4 serverResponse: read comm file: 15:29:05 INF - Server status = 135 15:29:08 [26493] 16 serverResponse: ERR - server exited with status 135 : client is not validated to perform the requested operation ...lines deleted...
TECH20718 | 2013-04-26
Technical Solutions | CMS-XML

NetBackup status code: 135

NetBackup status code : 135
HOWTO50904 | 2012-11-19
How To | CMS-XML

Media Manager status code 135

Media Manager status code 135
HOWTO51346 | 2012-11-19
How To | CMS-XML

NetBackup status code: 135

NetBackup status code : 135
HOWTO35014 | 2010-10-29
How To | CMS-XML

Media Manager status code: 135

Media Manager status code : 135
HOWTO35456 | 2010-10-29
How To | CMS-XML

SAP restore fails with " dbc_get_string: Output = EXIT STATUS 135" | Symantec Connect

SAP restore fails with " dbc_get_string: Output = EXIT STATUS 135" 10:29:29.398 [7485] <2> dbc_get_string: Output = EXIT STATUS 135 10:29:29.398 [7485] <16> VxBSAQueryObject: ERR - dbc_get_string() failed 135 10:29:29.398 [7485] <4> restore_one_fifo: System detected error, operation aborted.
Connect Forums | HTML

rman-10038 error when attempting to backup Oracle version 11.2 using NetBackup 6.x.

xbsa_validatefeatureid()+ 135 call VxBSAValidateFeatur 000000001 ? 7fffc2cfcbe0 ?
TECH77071 | 2014-03-14
Technical Solutions | CMS-XML

ms-sql restores fail with status code 2850

14:31:41.527 [3132.3152] 16 VxBSAQueryObject: ERR - dbc_get_string() failed 135
TECH211497 | 2014-01-28
Technical Solutions | CMS-XML

Restore of Bare Metal Restore (BMR) Windows client will fail with error message "Unable to Verify Backup" or "Failed to Verify Backup".

or hosts file or invalid routing back to the client. 3. The Master Server does not see the restoring client as a valid client (rc=131, 133, 135 ) The ip-address used by the client resolved to a different name than in the configuration, or the
TECH87087 | 2014-01-09
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pci1077,2422.1077.134 pci1077,2422.1077. 135 pci1077,2422.1077.136
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?