STATUS CODE 77: LiveUpdate of a Windows client fails with a NetBackup Status Code 77 (execution of the specified system command returned a nonzero status) when connecting with a UNIX or Linux LiveUpdate server.

Article:TECH59709  |  Created: 2009-01-18  |  Updated: 2009-01-18  |  Article URL http://www.symantec.com/docs/TECH59709
Article Type
Technical Solution


Environment

Issue



STATUS CODE 77: LiveUpdate of a Windows client fails with a NetBackup Status Code 77 (execution of the specified system command returned a nonzero status) when connecting with a UNIX or Linux LiveUpdate server.

Error



execution of the specified system command returned a nonzero status

Solution



Overview: LiveUpdate of a Windows client fails with a NetBackup Status Code 77 (execution of the specified system command returned a nonzero status) when connecting with a UNIX or Linux LiveUpdate server.

Troubleshooting: On the UNIX/Linux LiveUpdate server, review the path to the LiveUpdate files, and determine if there are any upper case letters in the path.  

Log files:  
In the LiveUpdate log file (found in the <install_path>\veritas\netbackup\logs\liveupdate directory on the Windows client), look for the following (bold added for clarity):
4/1/2008, 9:12:29 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server server_name.domain_name.com at path /lucontainer via a HTTP connection. The server connection attempt failed with a return code of 1834, LiveUpdate could not find this update file on the server.
4/1/2008, 9:12:29 GMT -> Progress Update: HOST_SELECTION_ERROR: Error: 0x802A0026
4/1/2008, 9:12:29 GMT -> LiveUpdate did not find any new updates for the given products.
4/1/2008, 9:12:29 GMT -> EVENT - SESSION END FAILED EVENT - The LiveUpdate session ran in Silent Mode. LiveUpdate found 0 updates available, of which 0 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 1834, LiveUpdate could not find this update file on the server.

Resolution:
Unlike UNIX and Linux, Windows is not case sensitive, So "LiveUpdate" is the same as "liveupdate" and "LIVEUPDATE" on a Windows machine.  The Windows LiveUpdate agent translates the configured URL into all lower case when making the LiveUpdate request to the UNIX/Linux LiveUpdate server.  Once the request reaches the UNIX/Linux LiveUpdate server, if there are upper and lower case characters in the path to the LiveUpdate files, the request to find these files fails, because the web server is merely mapping the URL to a directory path on the machine.

To resolve this issue, change the path name on the UNIX/Linux server to all lower case or use a Windows LiveUpdate server.  



Supplemental Materials

SourceError Code
Value77
Descriptionexecution of the specified system command returned a nonzero status


Legacy ID



302988


Article URL http://www.symantec.com/docs/TECH59709


Terms of use for this information are found in Legal Notices