cancel
Showing results for 
Search instead for 
Did you mean: 

Can't Get Updates

Alietr
Level 2
I had figured that Live Update was taking care of my BE11(7170) SP1 Backup updates on my Windows 2003 server, but that apparently wasn't so.  When I run LU, I am getting the LU1812 error.  I have tried all of methods previously mentioned in these forums, as well as what the various Symantec articles concerning the error recommend.

I have made sure I deleted everything in the LU Updates folder.  I have tried it logged in as the BackupExec account.  I have tried it without going through RDP.  I have made sure msxml3.dll is re-registered.  I have made sure all the BE services are stopped and the BE program is closed before running LU/installing patches.   I have tried to run LU from inside BE instead of on a standalone basis.  I am pretty sure the account has the correct permissions.  The results are always the same.

When I try to run patches individually, they all fail as well.  The same with installing SP4.  A small portion of a sample log reads thusly:

***Failed to write a message to the log server
Property(S): AppDataFolder = C:\WINDOWS\system32\config\systemprofile\Application Data\***Failed to write a message to the log server
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\***Failed to write a message to the log server
Property(S): CommonFilesFolder = C:\Program Files\Common Files\***Failed to write a message to the log server
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\***Failed to write a message to the log server
Property(S): FavoritesFolder = C:\WINDOWS\system32\config\systemprofile\Favorites\***Failed. went into writelog, but did not send to log server
Entering PatchSetup.exe***Failed. went into writelog, but did not send to log server
Command Line: /NAME:BEWS 11.0.7170 Hotfix 32 (32-bit) /UI:NONE***Failed. went into writelog, but did not send to log server
Executing GetPatchInfo.***Failed. went into writelog, but did not send to log server
1: 0 2: Symantec Backup Exec for Windows Servers.msi 3: {EAB0C0F9-B57B-4865-91A3-DE3B34B1FB02} 4: {EAB0C0F9-B57B-4865-91A3-DE3B34B1FB02}; 5: 0 6: 1 7: 1 8: 0 ***Failed. went into writelog, but did not send to log server
V-225-136: The patch failed to install. Return code: 1612 ***To search for information about this error, click <a href="http://support.veritas.com/umi/V-225-136" target="main">here </a> ***Failed. went into writelog, but did not send to log server
Exiting PatchSetup.exe***Failed. went into writelog, but did not send to log server
Entering PatchSetup.exe***Failed. went into writelog, but did not send to log server
Command Line: /NAME:BEWS 11.0.7170 Hotfix 34 (32-bit) /UI:NONE***Failed. went into writelog, but did not send to log server
Executing GetPatchInfo.***Failed. went into writelog, but did not send to log server
1: 0 2: Symantec Backup Exec for Windows Servers.msi 3: {EAB0C0F9-B57B-4865-91A3-DE3B34B1FB02} 4: {EAB0C0F9-B57B-4865-91A3-DE3B34B1FB02}; 5: 0 6: 1 7: 1 8: 0 ***Failed. went into writelog, but did not send to log server

None of the articles listed on the web page cited in the log provide any additional helpful information.  I will add one 'odd' note -- when I check BE on Windows Install/Remove programs, it says SP1 and HFs 19, 20, 21,18, 17, 24, 26, 23 and 22 are installed.  BUT, when I try to change BE, it says the program may have already been uninstalled.  When I check in BE itself, it does not indicate ANY updates are installed.

Short of having to reinstall BE from scratch (which I am loathe to do), do I have any additional options?

Thanks in advance,
Andy

1 ACCEPTED SOLUTION

Accepted Solutions

Ken_Putnam
Level 6

Can't suggest any way around those errors, but if you do need to re-install see


http://seer.entsupport.symantec.com/docs/307764.htm
http://seer.entsupport.symantec.com/docs/319367.htm

to save all your local configuration settings and data

View solution in original post

2 REPLIES 2

Ken_Putnam
Level 6

Can't suggest any way around those errors, but if you do need to re-install see


http://seer.entsupport.symantec.com/docs/307764.htm
http://seer.entsupport.symantec.com/docs/319367.htm

to save all your local configuration settings and data

Alietr
Level 2
Reinstalling seems to have worked.  It wasn't nearly as bad a process as I feared it would be.