Discussion Locked

Server Lock Up

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Netware 5 server that locks up when I put the application launcher for Zenworks in the login script. I have to do a reboot and that is not good. If I rem it out,and the NAL does not run,this does not happen. The zen database is on another Net5 server. The NAL is for the NT machines that causes the lockup. Any suggestions as to why this may happen?
I would appreciate any help, because I really need my Zenworks. Oh, it is Zenworks2 that I use,Netware 5sp5.

8 replies

by chris.riley

You say that the server 'locks up'. What happens exactly...does it abend, do you get any errors or does the utilization go high?

Does NAL actually run ok or does it 'hang'?

What version of the Novell Client for NT are you using?

Have you tried running NALEXPLD.EXE rather than NAL.EXE?

In the meantime check TIDs 10018969 and 10021485 on www.support.novell.com

Hope that helps,
Chris

by mike.booker

I use nalexpld.exe, the server is at the screensaver and you can not do anything with that. I am at 4.8 for NT. And as far as I can tell, it actually hangs. Users can not log in and it ends up a reboot for me.

by colin_joseph

Go to the server is question and load DSTRACE. The DS trace at the time of the lockup should tell you if there are any communications problems between the servers.

Make sure that you go to monitor.nlm and look under Kernel so that you can see what process is working the hardest when the NAL is executed..

by dangh

Try putting NALWIN32.EXE in the login script in place of NAL. The NAL.EXE is suppose to point to either the 16 or 32-bit EXE depending on the Workstation OS. In the case of Windows9x and NT it should run NALWIN32. I doubt that you are running any 16-bit OS's, so this should not be a problem. It has been my experience that NAL.EXE will often fail to run under certain configurations. Futhermore NT is notorious for its file locking. If one WS hangs on NAL.EXE and other WS's are trying to access it, it could cause your server to ping at 100% utilization.

This discussion is closed to new replies.