Netbackup The Server Returned Error Code 23
Symantec Connect User-to-user forums, blogs, videos, and other community resources on Symantec Connect. Status Code 107 ==================== Status code not available. Status Code 78 ==================== afs/dfs command failed Indicates an AFS vos command failure. o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. http://windowsazure4j.org/error-code/netbackup-server-error-code-23.html
On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 4. Direct the output of the wbak command to /dev/null to avoid filling up your file system and use the following parameters: -l -nhi -pdtu -stdout -nwla and -full or -af date Status Code 52 ==================== timed out waiting for media manager to mount volume The requested volume was not mounted before the timeout expired. Status Code 199 ==================== operation not allowed during this time period A user backup or archive was requested and this client is not in a policy that has the following: a https://support.symantec.com/en_US/article.TECH175412.html
Socket Read Failed 23 Netbackup Windows
A frequent cause is that the server's file system is full. Enable detailed activity logging on the client: o Create bpcd and bpbkar (UNIX or Windows NT only) activity log directories. A network problem or a problem with the process that writes to the socket can cause socket read failure. * A problem specific to NetBackup Snapshot Client (see recommended actions). Status Code 108 ==================== Status code not available.
Status Code: 29 Top Message: failed trying to exec a command Explanation: A command could not be executed. Status Code 184 ==================== tar had an unexpected error A system error that occurred in tar. This may be a permission problem. · On UNIX, a file could not be locked that has mandatory locking enabled. Netbackup Error Code 25 This error can occur if the system cannot allocate enough shared memory.
Then, retry the operation and check the resulting activity logs. 2. Exited With Status 23 Socket Read Failed On Macintosh clients, check the inetd and bpcd activity logs. With a UNIX client, the email was not sent to an email address specified with USEMAIL in the client's bp.conf file. https://www.veritas.com/support/en_US/article.TECH38975 The connection was terminated because VxSS authentication cannot be completed.
Status Code 89 ==================== problems encountered during setup of shared memory The NetBackup processes use shared memory for some operations. Clear Host Cache Netbackup Status Code 222 ==================== done This status code is used to coordinate communication between various NetBackup processes and is normally not seen. For detailed debug information: 1. The following are some possible causes: · I/O error writing to the file system · Write to a socket failed.
Exited With Status 23 Socket Read Failed
Status Code 209 ==================== error creating or getting message queue When a NetBackup process attempts to create an internal message queue construct for inter-process communication, an error occurs. b. Socket Read Failed 23 Netbackup Windows Status Code: 34 Top Message: failed waiting for child process Explanation: The bpsched process encountered a failure while waiting for a child process to complete. Netbackup Error Code 24 Status Code 21 ==================== socket open failed A socket was not opened.
For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. navigate here Status Code 264 ==================== Status code not available. Verify that the server list specifies the correct master server. On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems. 5. Netbackup Error Opening The Snapshot Disks Status 23
On UNIX systems, use the UNIX sum command to check for corrupt binaries. 51 52 53 54 55 56 57 58 59 Top Status Code: 50 Top Message: client process If that is not the problem: 1. Recommended Action: Try running wbak by hand to determine the source of the problem. Check This Out NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT.
Status Code 131 ==================== client is not validated to use the server The client name, as determined from the connection to the server, did not match any client name in the Bpclntcmd Status Code 48 ==================== client hostname could not be found The system function gethostbyname() failed to find the client's host name. Status Code 121 ==================== no media is defined for the requested NB database backup When NetBackup attempted to back up its internal catalogs, no media IDs were defined in the catalog
Status Code 233 ==================== premature eof encountered This status code is an intermediate one that usually precedes another status code and is associated with a problem in network communication.
Status Code 261 ==================== vault internal error 261 This error code should not occur. Go to Solution the Server returned Error Code 23 Zahid_Haseeb Level 6 Partner Accredited â€Ž08-02-2012 04:09 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Possible reasons for this error are as follows: * Media ID is already active in the NetBackup media catalog on this server * Media ID is not in the volume configuration On Windows, the server list contains no entries.
On the Performance tab, set Virtual Memory to a higher value. 4. On the other side of the connection, the other system is not configured to use VxSS. Compare the NetBackup version level on the server to that on the clients: o On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file. http://windowsazure4j.org/error-code/netbackup-error-code.html Setting the value to 0 disables backups and archives.
Status Code 255 ==================== Status code not available. On a Windows NT NetBackup server, set the Verbose option on the General tab in the Master Server Properties dialog box (see "Using the Configure - NetBackup Window" on page 57). For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Status Code 55 ==================== permission denied by client during rcmd The UNIX client does not have the server's name in its /.rhosts file.
Status Code 77 ==================== execution of the specified system command returned a nonzero status An immediate command returned a nonzero status. c. If the error occurs when executing a command on the command line, verify that the parameters are valid. 3. Sorry, we couldn't post your feedback right now, please try again later.
Status Code 263 ==================== session id assignment failed The unique identifier to be assigned to the Vault session is corrupt. This can occur because the backup job was terminated or the child process was terminated by another error. The maximum number is specified in the Media and Device Management volume configuration. On a Windows NT NetBackup server (master or slave), check the Event Viewer Application log for error messages that indicate why the tape mount did not complete.
Status Code 47 ==================== host is unreachable An attempt to connect to another machine failed. Status Code 243 ==================== the client is not in the configuration The specified client name was not in the catalog. Status Code 134 ==================== unable to process request because the server resources are busy Status code 134 is an informational message that indicates that all drives in the storage unit are Status Code 152 ==================== required value not set An incomplete request was made to the bpdbm process (on UNIX), or the NetBackup Database Manager service (on Windows).
For example, a NetBackup master server has NetBackup 6.5 and the media server or the client has NetBackup 4.5. Written by leading industry professionals, this blog is designed to stimulate discussion, drive thought, and suggest best practices to help readers better navigate the complex maze of federal business. Â© Copyright Status Code 198 ==================== no active policies contain schedules of the requested type for this client A user backup or archive was requested, and this client is not in a policy For example, a job fails with this error code if a policy is set up that specifies the following: * A storage unit that is on a SAN media server *
To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on Status Code 189 ==================== the server is not allowed to write to the client's filesystems The client does not allow writes from the server.