Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Network Load Balancing 2

Status
Not open for further replies.

LawnBoy

MIS
Mar 12, 2003
2,881
I'm getting an error on bootup in Event Viewer that say the NLB cannot start because it is disabled or there are no resources assigned to it. This is correct, I'm not using NLB and have no need to. How can I stop this error from popping up?

The NLB Manager shows no clusters assigned...

tia.

"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
It's not even installed, much less checked. On either adapter.

BTW, SP1.



"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
The only articles I can find on the KB tell me I don't have the clusters configured properly. Which is true, I don't have them configured at all.

Yes, I'm running BE 10d with AOFO.

Weird thing is, I have an exact replica (and I do mean exact) of this server built a few months ago that does not throw this error.

I first saw this problem a few weeks ago, no harware or software changes had been done, and previous boots didn't error.

"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
That Veritas link solved it. Thanks very much!


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
Awesome PCE. I've had these errors for ever, but they weren't causing any problems and I haven't had time to research. I would have never guessed it had anything to do with Backup Exec.
 
Me neither.


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 
Fortunately it started just after i had installed it on a box so i had a fair idea it was that otherwise i probably would have been stumped as well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top