cancel
Showing results for 
Search instead for 
Did you mean: 

LiveUpdate - same setup, mostly works, couple machines won't update

Lynne_Seamans
Level 6

So, I put on NetBackup maintenance release 7.5.0.3, and also put the appropriate files in my LiveUpdate directory (use https, from my windows 2008r2 master server)

Went to update clients using LiveUpdate.

Most of them worked just fine, so I guess the general setup is OK. However, I have a couple machines that keep erroring -- each of them has a "sister" machine that is much the same and that works fine, so I'm stumped.

Think I'll open a ticket, but you know support, doing some legwork on my own.  Any ideas what logs I should look at or turn on or what on those couple windows 2008 clients that won't upgrade?

Here's the messages I'm getting:

 

8/7/2012 10:07:37 AM - Info nbliveup(pid=14156) Updating LiveUpdate Server location to: http://netmast.muad.local/LiveUpdate       
8/7/2012 10:10:34 AM - requesting resource netmast.muad.local.NBU_POLICY.MAXJOBS.mu-lu-windows
8/7/2012 10:10:34 AM - granted resource netmast.muad.local.NBU_POLICY.MAXJOBS.mu-lu-windows
8/7/2012 10:10:34 AM - started process RUNCMD (9384)
8/7/2012 10:10:34 AM - ended process 0 (9384)
8/7/2012 10:08:07 AM - Error nbliveup(pid=14156) Error executing "C:\Program Files (x86)\Symantec\LiveUpdate\LUALL.EXE" -s -h "C:\Program Files\Veritas\NetBackup\LiveUpdateHost.hst", stopping update.  
8/7/2012 10:08:07 AM - Info nbliveup(pid=14156) Start of the pack summary file:       
8/7/2012 10:08:07 AM - Info nbliveup(pid=14156) 01/09/12 15:34:34 Installed Symantec NetBackup 7.1.0.2 (7.1 Release Update 0 HotFix 2)
8/7/2012 10:08:07 AM - Info nbliveup(pid=14156) 04/10/12 08:40:47 Successfully installed NetBackup 7.5 Client.      
8/7/2012 10:08:07 AM - Info nbliveup(pid=14156) 05/03/12 14:43:11 Installed Symantec NetBackup 7.5.0.1 (7.5 Release Update 0 Maintenance Release 1)
8/7/2012 10:08:07 AM - Info nbliveup(pid=14156) End of the pack summary file:       
8/7/2012 10:08:07 AM - Info nbliveup(pid=14156) EXIT STATUS 77          
8/7/2012 10:10:34 AM - requesting resource netmast.muad.local.NBU_POLICY.MAXJOBS.mu-lu-windows
8/7/2012 10:10:34 AM - granted resource netmast.muad.local.NBU_POLICY.MAXJOBS.mu-lu-windows
8/7/2012 10:10:34 AM - started process RUNCMD (9384)
8/7/2012 10:10:34 AM - ended process 0 (9384)
execution of the specified system command returned a nonzero status(77)

4 REPLIES 4

mph999
Level 6
Employee Accredited

 <install_path>\veritas\netbackup\logs\liveupdate is the log you want.

Regards,

Martin

Lynne_Seamans
Level 6

Yup, they were right there.  Don't exactly know what they're trying to tell me..    It says something about "expired subscription" but other windows machines updated correctly from the NBU Master Server:

 

8/7/2012, 15:55:22 GMT -> Added package to cache...

8/7/2012, 15:55:22 GMT -> DIS - LAUNCHEX("C:\ProgramData\Symantec\LiveUpdate\Downloads\Updt701", "setup.exe", "-LIVEUPDATE", 1) <BEGIN>

8/7/2012, 15:55:22 GMT ->         Launching commandline C:\PROGRA~3\Symantec\LIVEUP~1\DOWNLO~1\Updt701\setup.exe -LIVEUPDATE.

8/7/2012, 15:59:13 GMT ->         Executable returned error code -2144731101.

8/7/2012, 15:59:13 GMT -> DIS - LAUNCHEX(0x802A0023) <END>

8/7/2012, 15:59:13 GMT -> Progress Update: PATCH_ERROR: Patch File: "C:\ProgramData\Symantec\LiveUpdate\Downloads\Updt701\1338988078jtun_nb_7.5.0.3.winnt.x64.zip", Script File: "C:\ProgramData\Symantec\LiveUpdate\Downloads\Updt701\Install_Update.dis", HR: 0x802A0023

8/7/2012, 15:59:13 GMT -> HR 0x802A0023 DECODE: E_DIS_LAUNCHEX_FAILED_PROCESS_EXIT_CODE

8/7/2012, 15:59:13 GMT -> Progress Update: PATCH_FINISH: Patch File: "C:\ProgramData\Symantec\LiveUpdate\Downloads\Updt701\1338988078jtun_nb_7.5.0.3.winnt.x64.zip", Script File: "C:\ProgramData\Symantec\LiveUpdate\Downloads\Updt701\Install_Update.dis", HR: 0x802A0023

8/7/2012, 15:59:13 GMT -> HR 0x802A0023 DECODE: E_DIS_LAUNCHEX_FAILED_PROCESS_EXIT_CODE

8/7/2012, 15:59:13 GMT -> EVENT - PRODUCT UPDATE FAILED EVENT - Update available for Symantec NetBackup x64 Windows - 7.5 - English. Update for Hotfix takes product from update 0 to 20120615. Server name - netmast.muad.local, Update file - 1338988078jtun_nb_7.5.0.3.winnt.x64.zip, Signer - cn=Symantec Corporation,ou=Locality - Culver City,ou=Product Group - LiveUpdate,ou=SymSignature 2005,o=Symantec Corporation, package install code 0. The Update executed with a result code of 1812, => The install script for this update was unable to launch a file it needed.  LiveUpdate aborted the update install.

8/7/2012, 15:59:14 GMT -> Progress Update: PATCH_PROCESSING_FINISH: Number of patches: 1, Num successful: 0

8/7/2012, 15:59:14 GMT -> Product = SESC Virus Definitions Win64 (x64) v11, Version = MicroDefsB.CurDefs, and Language = SymAllLanguages was aborted from this LiveUpdate session.

8/7/2012, 15:59:14 GMT -> Reason for product being aborted => This product was not updated due to a processing error.

8/7/2012, 15:59:14 GMT -> EVENT - PRODUCT UPDATE FAILED EVENT - Update available for Antivirus and antispyware definitions - MicroDefsB.CurDefs - SymAllLanguages. Update for  takes product from update 0 to . Server name - , Update file - , Signer - , package install code 0. The Update executed with a result code of 1845, => This update was aborted during LiveUpdate Pre-session processing.  This error is most likely due to an expired content subscription.

8/7/2012, 15:59:14 GMT -> EVENT - SESSION END FAILED EVENT - The LiveUpdate session ran in Silent Mode. LiveUpdate found 1 updates available, of which 0 were installed and 1 failed to install.  The LiveUpdate session exited with a return code of 1806, LiveUpdate downloaded all of the updates you requested, but was unable to install any of them.

8/7/2012, 15:59:14 GMT -> ***********************           End of LU Session           ***********************

mph999
Level 6
Employee Accredited

Error seems a bit generic, this TN matches.

 http://www.symantec.com/docs/TECH128283

Regards,

Martin

Lynne_Seamans
Level 6

I did open a ticket with support on this.  They told me to uninstall and re-install LiveUpdate on the problematic machines.  Typically lame support answer!

It helped with some machines but not others.  I did not bother to pursue.