NLMs can't be loaded
sola...@yahoo.ca
drivers, LSL.nlm, SGUID.nlm, CONNMGR.nlm, LFS.nlm, FILESYS.nlm, mounts
volum SYS. After that evrything goes wrong. The most of modules can not be
loaded. I see error records rushing up on the screen very fast. At last I
have normal consol as ussualy. But I can't load any modules like monitor.
nlm, inetcfg.nlm, nwconfig.nlm, dsrepair.nlm, vrepair.nlm and other.
Instead of having modules working I have messages like that "Read post end
of read buffer" or "Error reading load file" or "Module *.nlm cannot be
loaded until *.nlm is loaded". Of couse instead of "*" there is a module
name. I cannot accsses my server by network too. What can I do to have my
server working properly?
Thanks a lot.
Massimo Rosen
sola...@yahoo.ca wrote:
>
> I have my NW5.1 server crashed down. It begins to start up properly, loads
> drivers, LSL.nlm, SGUID.nlm, CONNMGR.nlm, LFS.nlm, FILESYS.nlm, mounts
> volum SYS. After that evrything goes wrong. The most of modules can not be
> loaded. I see error records rushing up on the screen very fast. At last I
> have normal consol as ussualy. But I can't load any modules like monitor.
> nlm, inetcfg.nlm, nwconfig.nlm, dsrepair.nlm, vrepair.nlm and other.
> Instead of having modules working I have messages like that "Read post end
> of read buffer" or "Error reading load file"
Your dos partition is obviously corrupt. You should start by *carefully*
checking it with scandik for instance, but be prepared that you have
lost data there. The easiest way to fix it (once the partition is
repaired) is to copy the c:\nwserver files from a working server running
the same OS and service pack.
CU,
--
Massimo Rosen
Novell Support Connection Sysop
No emails please!
http://www.cfc-it.de
sola...@yahoo.ca
I have formated DOS partition and copied "C:\NWSERVER" to the one frome an
other server which the same. Now I have error "NISI CCS: FATAL -
Initialization error. Controlled cryptography Services are not available.
Loading module POLIMGR.NLM". Modules like nwconfig.nlm, monitor.nlm, etc.
can be loaded but value SYS can not. It says there are no any netware
partitions.
Massimo Rosen
Have you modified the startup.ncf you copied over so that the correct
drivers are loaded again? If your storage drivers load succesfully and
see all your physical disks, but Netware itself can't see any Netware
partition any longer, then the corruption on your disks were far more
severe than just in the Dos partition. If you're lucky, only the
partition table is toast and there may be a chance to repair that. If
you're not, you may have lost your Netware data, and need to restore.
You may have a look at storagemanager from portlock (www.portlock.com),
in many cases it is able to repair logical disk problems. If, however
your drive is failing physically, there's probably not much you can do.
solayris
> Have you modified the startup.ncf you copied over so that the correct
> drivers are loaded again? If your storage drivers load succesfully and
> see all your physical disks, but Netware itself can't see any Netware
> partition any longer, then the corruption on your disks were far more
> severe than just in the Dos partition. If you're lucky, only the
> partition table is toast and there may be a chance to repair that. If
> you're not, you may have lost your Netware data, and need to restore.
> You may have a look at storagemanager from portlock (www.portlock.com),
> in many cases it is able to repair logical disk problems. If, however
> your drive is failing physically, there's probably not much you can do.
>
> CU,
You were right. I didn't modify the startup.ncf but now I have done it. So
the problem still exists. I think it is because of one defrences in both
servers hardware. The working properly server has IDE drive where DOS and
valume SYS are located but crushed server has not any IDE disks and DOS
partition and valume SYS are located on SCSI drive.
Massimo Rosen
solayris wrote:
> You were right. I didn't modify the startup.ncf but now I have done it. So
> the problem still exists. I think it is because of one defrences in both
> servers hardware. The working properly server has IDE drive where DOS and
> valume SYS are located but crushed server has not any IDE disks and DOS
> partition and valume SYS are located on SCSI drive.
Did you copy the necessary SCSI storage drivers to c:\nwserver? Does
your driver load? Alos, if it does, does it autoload scsihd.cdm, and is
that in c:\nwserver too?
solayris
wrote:
>
> Did you copy the necessary SCSI storage drivers to c:\nwserver? Does
> your driver load? Alos, if it does, does it autoload scsihd.cdm, and is
> that in c:\nwserver too?
>
> CU,
Yes, they all are loaded.
--
Отправлено M2, революционной почтовой программой Opera:
http://www.opera.com/
Massimo Rosen
solayris wrote:
>
> On Tue, 27 Jan 2004 17:58:52 GMT, Massimo Rosen <mros...@spamcfc-it.de>
> wrote:
>
> >
> > Did you copy the necessary SCSI storage drivers to c:\nwserver? Does
> > your driver load? Alos, if it does, does it autoload scsihd.cdm, and is
> > that in c:\nwserver too?
> >
> > CU,
>
> Yes, they all are loaded.
Oh well. Please post the output of "list devices" here. If it correctly
show all your logical disks, I'm afraid your partition table is corrupt.
Your only option at this point is either apiece of software that may be
able to repair that like Storage Manager that I posted before, or some
external help by someone that knows it's way around in a diskeditor and
knows how to repair partition tables. But even in that case, vital parts
of your data might have been overwritten already, and might be lost
beyond any repair. In that case I can just hope you have a good backup.
solayris
wrote:
>
> Oh well. Please post the output of "list devices" here. If it correctly
> show all your logical disks, I'm afraid your partition table is corrupt.
> Your only option at this point is either apiece of software that may be
> able to repair that like Storage Manager that I posted before, or some
> external help by someone that knows it's way around in a diskeditor and
> knows how to repair partition tables. But even in that case, vital parts
> of your data might have been overwritten already, and might be lost
> beyond any repair. In that case I can just hope you have a good backup.
>
> CU,
I have set up new server on the server on other SCSI disk, installed
support pak 5 and eDirectory ( both like on crushed server). After that I
copied C:\server to DOS partition of crushed disk and started server up.
It started and valume SYS loaded but there are some errors and an abend. I
cannot get accsses to NDS. I try load DSREPAIR but it say "Could not gain
access to Directory Services DS.NLM is not loaded".
Abend sometime like that:
Server halted Thursday, 29 January 2004 16:51:35.773
Abend 1 on P00: Server-5.00k: Page Fault Processor Exception (Error code
00000000)
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 0000001C EBX = D3F743A0 ECX = 00000006 EDX = D464A960
ESI = 00000000 EDI = 00000000 EBP = D3F722A0 ESP = D3F72280
EIP = D4BD46BC FLAGS = 00214246
Address (D4BD46BC) exceeds valid memory limit
EIP in UNKNOWN memory area
Access Location: 0xD4BD46BC
and go on...
or
Server MOSCOW halted Thursday, 29 January 2004 17:24:57.204
Abend 1 on P00: Server-5.00k: Page Fault Processor Exception (Error code
00000000)
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000000 EBX = D38FB040 ECX = 00000001 EDX = 00000001
ESI = D7BC9000 EDI = 00000000 EBP = D7BCF0C0 ESP = D7BC8DB0
EIP = D369EB53 FLAGS = 00214246
D369EB53 8B90BB030000 MOV EDX,[EAX+000003BB]=?
EIP in REQUESTR.NLM at code start +00000B53h
Access Location: 0x000003BB
The violation occurred while processing the following instruction:
D369EB53 8B90BB030000 MOV EDX,[EAX+000003BB]
D369EB59 42 INC EDX
D369EB5A 83C408 ADD ESP,00000008
D369EB5D 8990BB030000 MOV [EAX+000003BB],EDX
D369EB63 8B8424BC000000 MOV EAX,[ESP+000000BC]
D369EB6A C70000000000 MOV [EAX],00000000
D369EB70 89F8 MOV EAX,EDI
D369EB72 81C4A0000000 ADD ESP,000000A0
D369EB78 5D POP EBP
D369EB79 5F POP EDI
Massimo Rosen
solayris wrote:
>
> I have set up new server on the server on other SCSI disk, installed
> support pak 5 and eDirectory ( both like on crushed server). After that I
> copied C:\server to DOS partition of crushed disk and started server up.
> It started and valume SYS loaded but there are some errors and an abend.
Well, that's much better. Read and follow:
http://developer.novell.com/research/sections/netsupport/networkts/2001/april/z010401.htm
And tell me exactly where and when the first error occurs.
solayris
wrote:
> Hi,
>
> solayris wrote:
>>
>> I have set up new server on the server on other SCSI disk, installed
>> support pak 5 and eDirectory ( both like on crushed server). After that
>> I
>> copied C:\server to DOS partition of crushed disk and started server up.
>> It started and valume SYS loaded but there are some errors and an abend.
>
> Well, that's much better. Read and follow:
> http://developer.novell.com/research/sections/netsupport/networkts/2001/april/z010401.htm
>
> And tell me exactly where and when the first error occurs.
>
> CU,
Very usefull article. I performed LOADSTAGE command and found out that
NICI did not work properly.
Performing "LOADSTAGE 3" I obtained following:
CCS.NLM: Waiting to initialize (0 minutes)
NICI is probably not fully installed or an XEBG did not load after a
system restart.
This message appears at system installation time untill NICI
installation is complete
but does not indicate a NICI malfunction.
Loading module PMLODR.NLM
.........................
Loading module POLIMGR.NLM
............All rights reserved.
Lib0-5.0-1001: Notice: No IPX or TCP/IP protokol primitives presentli
available.
Lib0-5.0-1002: Notice: No UDP or TCP/IP protokol primitives presentli
available.
Lib0-5.0-1001: Notice: No IPX or SPX protokol primitives presentli
available.
LOADSTAGE 4
DS.NLM error initializing function 38, -666
Acording to the article I have complited all steps recomended. I
downloaded nrepair3.exe from ftp.novel.com, loaded nrepair.nlm, removed
NICI. After successfully removing NICI from my server, got the *.NFK file
from my server base license disk, and copied that file to the SYS:SYSTEM
directory while renaming the file to NICIFK (with no extension). But after
server downing I got the same resolt as I have described abow.
I still have not accesse to NDS on my server.
solayris
Now I have only problem like that
CCS.NLM: Waiting to initialize (0 minutes)
> NICI is probably not fully installed or an XEBG did not load after a
> system restart.
> This message appears at system installation time untill NICI
> installation is complete
> but does not indicate a NICI malfunction.
>
> Loading module PMLODR.NLM
> .........................
> Loading module POLIMGR.NLM
> ............All rights reserved.
> Lib0-5.0-1001: Notice: No IPX or TCP/IP protokol primitives presentli
> available.
> Lib0-5.0-1002: Notice: No UDP or TCP/IP protokol primitives presentli
> available.
> Lib0-5.0-1001: Notice: No IPX or SPX protokol primitives presentli
> available.
The DS is open and I have had access to NDS. But I cannot gain server by
IPX/SPX.
Massimo Rosen
solayris wrote:
>
> The DS is open and I have had access to NDS. But I cannot gain server by
> IPX/SPX.
*Much* better. So I assume you solved the nici problem, and are now no
longer getting any errors when the server boots?
Can you give me a few more details about that IPX issue? Do you have a
serverid in the autoexec? Does autoexec get executed at all?