Backup Exec 9 & Win 2003 Server Errors on Start 1

[debsw1]

Installing Veritas BackupExec 9 (4454) on a Windows Server 2003 Standard edition.

After the install of BackupExec i get a "Service failed to start" message and the event viewer tells me it's the 'Network Load Balancing Service" which has failed. Network Balancing is not being used and not setup. The server has a single NIC and IP.

Have installed same version on 2000 and no problem. Why is BackupExec trying to start the service? Does it need it? Any ideas would be much appreciated.

 

[dogmata]

Debsw1:

More details please:

A) what happens after you uninstall BE and reboot > does it still whinge about the NLB service > if so, BE is not the problem or, disable all BE services (incl. the MSSQL$BKUPEXEC service and then boot > does it still moan, again its not BE

B) What do the event viewers say ? Easiest way would be to save and then clear out the system and applicationlogs > boot, and you will have captured a fresh set of logs, see what event ID's you get

C) what is running on that box ?

D) Not entirely sure but, you should have a bkupinst.log in the root of the winnt (or "windows"&quot directory > search for "return value 3" >> this indicates a critical error of some sort >> check their website.

E) if you dont use it, why not just remove the components/service via local area connection properties ?

F) Dont think BE would use it but, check each BE service's properties > dependency tab > see if one of their service relies on it, probably not would be my guess

Cheers
Dog

 

[debsw1]

Dog

a) When BE isn't installed or uninstalled then we don't get the error.

b) We get event id: 7000 Service Control Manager, the Network Load Balance Service Failed to Start.

c) Windows Server 2003 Standard and Veritas Backup Exec V9 Latest Revision (4454), have also tried with earlier revision.

d) Will check this out.

e) Have done this and still get the error.

f) None of BE services rely or are dependent on it.

Thanks for assistance
Debbie

 

[debsw1]

Dog

Thanks for help but have found answer, Microsoft Knowledgebase Doc No: 268437, apparently even though NLB is not installed some NLB registry keys may be present in registry, Veritas must of been activating these registry entries some how.

Debbie

 

[Greasemonkey1]

I ran in to the same problema and all you have to do is start that services in the Veritas software.

 

[pctekk]

Does anyone know if you can backup a Win 2003 server
from a Win 2000 Adv. Server w/ BE 8.6 ??

I tried to install the RA on the remote win 2000 Adv. Srv
but it didnt take.

thanks for any info/direction.

BigL

 

[dogmata]

pctekk: the answer is no. Only the updated build of 9.0 (rev 4454 is the new one, rev 4367 is the older build) supports 2003 fully.

 

[tonyfac]

Greasemonkey1

You said "I ran in to the same problem and all you have to do is start that services in the Veritas software."

This might be a dumb question, but how do you do that? I am getting the same error on boot and am pulling my hair out trying to get rid of it. Thanks for the help.

 

[Kopfjager]

Follow Debs Microsoft KB article to fix that error. There is nothing in Backup Exec to start that will fix that error.

 

[pctekk]

Dog,

How come you cant See the System states using v9.0 of BE ??

is that the norm ??

 

[Kopfjager]

The system start is now listed underthe Shadow Copy Componants in 9.0 Shadow Copy is Microsoft's version of Open File option and can be used instead of Veritas' Advanced Open File Option.

 

[Mark1230]

We have had the same problem and one of the guys here spent about an hour on hold with Veritas support.

To be told... New version for Win2003 !!! surprise

So get in touch with Veritas and they will send you a new CD... unless you want to download 300Mb.

RD