I have the same errors when running LiveUpdate v3.0.0.160 manually. BE 11.0.6235 with HotFix 2 running on Windows Server 2003 R2 Standard x64 Edition.

Seems strange that it's trying to install "Symantec Backup Exec (TM) 11d for Windows Servers," since it's already installed. Maybe that's just a generic update name.

i have had the above also happen to me. I get it mainly if Backup Exec is carrying out other tasks at the same time as trying to do a liveupdate.

I installed Hotfix #2. Didn't fix the problem.

Hi,

Please refer to:

How to manually run the updates using LiveUpdate in Backup Exec 11d

http://support.veritas.com/docs/286530

Regards
Padmaja

As per my first post it fails when done automatically and when I try it manually.

Hello,



Could you change the internet options to allow the active x controls and pugins..




Thank You,


Shweta

Already done. Tried putting it into my trusted sites, turning off all checks, etc.

To determine what is causing this issue, it is important to differentiate whether the problem is a LiveUpdate issue or a patch installation issue. In general, LiveUpdate is a patch delivery system. LiveUpdate will download and will initiate the patch installation. If the patch fails to install, this is a patch issue; not a LiveUpdate issue. According to the post, it looks like the patch downloaded fine so the patch installation log needs to be examined.

Look in the Backup Exec installation log (BKUPINST.HTM) for information on why the patch failed to install. You should be able to search for the following text in the log to find the begining of the patch installation (there will be multiple entries for this text if you tried to install the patch multiple times):

"Symantec Backup Exec (TM) 11 for Windows Servers Patch Log :"Message was edited by:
Steve Broomell

I'd be very concerned about automatic Veritas updates in the first place.

Just look at the mess that SP4 caused with version 9.1.

Download the update yourself and apply it. See if it works. That will also answer the previous question on whether you have a patch issue, or a liveupdate issue.

This is what happened when I tried a manual update:

Live updated dowloaded the updates you requested but all of them failed to install

IT DOES NOT WORK




I have been trying to fix backup issues for two hours this morning, plus I logged on last night and this morning from home to check them. Why is this product so poor, does anyone else feel this way.

But even though you did it manually, it sounds like you're trying to use Liveupdate.

Go to the Veritas website, hunt ( it will take you a while ) for the updates, download them and when you have a .exe file saved on your C:, try running it and see what happens.

Support pointed me to http://service1.symantec.com/SUPPORT/sharedtech.ns...

This wouldn't run on my server (2003 Std R2 x64 w/IE7). After messing around with IE7 trying to get it to work I finally gave up and uninstalled IE7 and was able to get it to run under IE6.

This cleaned up the LiveUpdate files. Manual updating now works. The automated update still shows "Could not start" under scheduled tasks.


Searching Symantec's web site for updates isn't a good solution. The ability to do a mass update is a good feature, one that Veritas has needed. The less time I spend searching for updates the better. That method is rapidly going the way of Win95, Bob, and Xenix.

Regardless, Symantec needs to fix the automatic download/update as it doesn't work.

Philip,
I agree. This product does not work well. Actually, it's quite poor quality.

There should be a stiky thread with all the known bugs. I suspect it would be massive.

Well, it turns out the reason LiveUpdate was erroring out was because I was running it from a TS session. That shouldn't make a difference or at the very least it should pop up a warning box.

Tape libraries and servers are usually in a server room and management is usually done remotely. Since TS is Microsoft's tool for remote logons it doesn't make sense to not support it.


Automatic scheduled updates still don't work.

Hi,

I've encounter the same problem, and YES! it's related to running liveupdate from a terminal window. It works fine when running off the console. However you do not need to use the console, you can run the RDP client in console mode using the following:

Start, Run:
mstsc /v:servername /console

This will emulate console, and let you run liveupdate remotely.

I would however like to add that this is pretty poor quality from Symantec.

yup, no go using TS/RDP, however, mstsc /v:servername /console works like a charm...
thanks!

I have the same problem, or so it seems, but not matter what I do my updates fail. Live Update via RDC, Live Update using mstsc /console, Live Update via the console directly or even manually trying to run the update. I get FAILED. Any help would be helpful.

Windows Server 2003 Standard R2
Backup Exec 11d
Microsoft SQL 2000 on a seperate server