Discussion Locked

BIG PROBLEM

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

We are running Netware5.1, it's being used as a file and print server.
Just recently we have upgraded from 4.1 to 5.1
It was running fine until last week the server popped up a few abends. The admin quickly rebooted the server before anyone had achance to look at the errors. I think "someone" was playing with it at the time. Anyways, after the reboot the NDPS and the broker that manages printing will not load. It comes back with -5 error. I looked it up and found out that it has something to do with the SAS which is supposed to authorize the loading of services. I also found out that it might be because there is not enough memory. I don't think that's the case because the server has 1Gig RAM, unless there is a memory leak.
For now theNDPS and the Broker are running on a separate machine, but that's just temporary solution untill we can fix the server.
Anyone has any ideas, please help!

This is what I got from abend.log
Server MS_FS1 halted Thursday, May 17, 2001 1:04:54 am
Abend 1 on P00: Server-5.00j: Page Fault Processor Exception (Error code 00000000)
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000000 EBX = 00000001 ECX = 00000006 EDX = D41936A0
ESI = 00000001 EDI = 00000001 EBP = D03BA2E0 ESP = D41F78C8
EIP = D04A66BC FLAGS = 00210286
Address (D04A66BC) exceeds valid memory limit
EIP in UNKNOWN memory area
Access Location: 0xD04A66BC

The violation occurred while processing the following instruction:

Running process: NWConfig Process
Created by: NetWare Application
Thread Owned by NLM: NWCONFIG.NLM
Stack pointer: D41F7664
OS Stack limit: D41EDB20
Scheduling priority: 67371008
Wait state: 5050170 (Blocked on keyboard)
Stack: D415DD3A (NWCONFIG.NLM|SetInstallChildNLMReturnCode+FC8)
this is the last abend in the log

7 replies

by kbnet

Suggest the following:

Have tried running dsrepair to check to see if you have any problems with your directory...

Have you tried loading NDPS after the server is up in running and not through a command in you autoexec.ncf file

Have you tried recreating the NDPS objects in your tree on the troubled server, maybe they somehow got corrupted when someone was playing with the server...

by kcraycraft

I would run a dsrepair first.
and i would check the ndps nds objects with nwadmin. It is possible one is corrupted or there is a job stuck somewhere

by tlb

Based on the information from the Abend.log, it looks like something may have changed in your startup files. It was in NWCONFIG and possible in the install product section. Maybe something was removed or added, and the startup files changed.

That's where I'd look first.

This discussion is closed to new replies.