NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 46

Media Manager status code 46
HOWTO104427 | 2014-11-20
How To | CMS-XML

Device management status code 46

Device management status code 46
HOWTO104672 | 2014-11-20
How To | CMS-XML

NetBackup status code: 46

NetBackup status code : 46
HOWTO103976 | 2014-11-20
How To | CMS-XML

Media server connection issues. Exit status 46

Media server connection issues. Exit status 46
TECH143742 | 2014-07-23
Technical Solutions | CMS-XML

Vmware policy validation fails and backups exit with status 156 on an ESX environment BPCD logs contains the error server not allowed access ( 46 ) on the Backup Host

When running a Admin Console on a Netbackup Client and configuring a Vmware Backup Policy the bpfis log is not updated and the bpcd log has error. server not allowed access ( 46 ) on the Backup Host The Host referenced is the Workstation running the Admin Console.
TECH162773 | 2013-11-27
Technical Solutions | CMS-XML

STATUS CODE: 46 Connecting to the Windows Remote Administration console fails with connection errors

server not allowed access( 46 )
TECH19944 | 2013-04-25
Technical Solutions | CMS-XML

STATUS CODE: 46 Restore fails with a Status Code 46 when attempting to restore data from one media server to another media server, when both servers have the same master server.

46
TECH11400 | 2013-04-25
Technical Solutions | CMS-XML

STATUS CODE 26 and 46: When using Veritas NetBackup (tm) for Vault, a catalog backup fails with status 26 (client / server handshaking failed) when backing up a Media Server and the exit status 46 (server not allowed access) is found in the admin log.

2 logconnections: BPCD CONNECT FROM x.x.x.x.866 TO x.x.x.x.13782 2 getBEorNBHostInfo: BPCD on nbmedia01 exited with status 46 2 bpgetdebuglog: server not allowed access
TECH38931 | 2013-04-25
Technical Solutions | CMS-XML

Status 59 and/or 46 errors seen during backups

Status 59 and/or 46 errors seen during backups
TECH141842 | 2013-04-25
Technical Solutions | CMS-XML

Inconsistent name resolution behavior causes intermittent status 46 and status 59

Inconsistent name resolution behavior causes intermittent status 46 and status 59
TECH204794 | 2013-04-06
Technical Solutions | CMS-XML

Configuring a new client from the master server produces status codes 46 and 59 if the master server has multiple NICs (Network Interface Cards.)

After adding a new client, attempting to configure it from Host Properties on the master server fails with status 46 . Backing up the client fails with status 59.
TECH195139 | 2013-03-25
Technical Solutions | CMS-XML

Restores started by Master Server are successful, but attempts to restore through a specific machine (not a Master or Media Server) fail with status 46, 59 and 25

Restores started by Master Server are successful, but attempts to restore through a specific machine (not a Master or Media Server) fail with status 46 , 59 and 25
TECH69399 | 2011-08-16
Technical Solutions | CMS-XML

Backup of client exited with status 46; server not allowed access

Backup of client exited with status 46 ; server not allowed access
TECH53996 | 2010-01-27
Technical Solutions | CMS-XML

NetBackup Host Properties of PureDisk node is getting an error 46 - server not allowed to access SPA

NetBackup Host Properties of PureDisk node is getting an error 46 - server not allowed to access SPA
TECH130578 | 2010-01-27
Technical Solutions | CMS-XML

Storage unit characteristics mismatched to request (status code 154)

11/21/2008 5:36:44 PM - requesting resource lin04- x86.nbu_policy.MAXJOBS.mapped_vm 11/21/2008 5:36: 46 PM - Error nbjm(pid=4224) NBU status : 154, EMM status : Storage unit is not compatible storage unit characteristics mismatched to request(154)
HOWTO70804 | 2012-02-08
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?