NetWare 5.1 SP8, eDir. 8.7.3.10, NICI 2.6.8 . . .

'Not sure what else I can check on this. (Spent the whole
night rebooting, copying .nfk files to NICIFK, etc.)

We rebooted the server, after making some changes towards
going over to a new ISP with new Public IP addresses, and our
one server went into the above error.

TID 10078840 - suggested bringing up the server in vrepair,
but no errors were found.

TID 10065538 - recommended several steps . . . but none
of them seemed to work:

- I reinstalled NICI 2.6.8 several times � I even manually copied
the files to their intended locations � after checking to see if there
were any read-only attributes on the original files. N.G.

- NREPAIR.NLM doesn't seem to do a thing. The files in
SYS:SYSTEM\NICI continued to need to be manually deleted.

- There is no XMGRCFG.DA0 in my _NETWARE directory.

- I've copied over all the .XLM files in C:\NWSERVER from
another server, replacing them, as well as replacing them
with my installs. [The DOMXENG.XLM and NOVXENG.XLM
files have the same date and file size . . . even so, I tried
copying the DOMXENG.XLM file over NOVXENG.XLM.]

- I tried using several copies of .nfk files from network locations
where they were saved � as well as from a floppy � but the
same results.

- The NICIFK file isn't "consumed" after the reboot, it's still there.

- The error message appears with every other boot. (We're
currently up � although not entirely: RconsoleJ and the
Novell Management Portal aren't responding.)

Any suggestions would be appreciated!


-Steve

Tried stepping through the startup, using the "server -kf8" command . . .
the server returned the "NICI CCS Fatal Initialization error" immediately
after loading the SLP.NLM module.

Tried updating SLP to version 2.13 but the same thing happens.

DISPLAY SLP SERVICES doesn't report any services for this server,
although all of our other NetWare servers are listed.

We have two SLP DAs . . . both are Statically configured in the
SLP.CFG file, using IP addresses. Both are successfully detected
from this server using the DISPLAY SLP DA command.


-Steve

The SLP portion of the problem has been resolved: we were
missing a value (Monitor) for the "SLP Scope List". Once this
was added and SET SLP RESET = ON was run on our servers,
the server started showing its services.

Still showing intemittent NICI errors, though.

I'm testing delaying the load of two modules, in case they're
loading too quickly:

?load httpstk.nlm /SSL /keyfile:"SSL CertificateIP"
?load portal.nlm

-SC

Steve Conrad,
> I'm testing delaying the load of two modules, in case they're
> loading too quickly:
>
That can also be the case. You can try singlestepping the server
startup with server -KF8

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Still failing. Intermittently I can bring the system up without the
"NICI CCS: Fatal Initialization error".

When I step through the startup (-KF8) and it fails, it always
fails after SLP.NLM loads and before PMLODR.NLM. I've tried
replacing the SLP.NLM and SLPTCP.NLM modules, but I'm having
the same results.

When I run NREPAIR it tells me the "Cryptographic components
are not initialized yet. You must reboot your server to initialize those
components. If rebooting doesn't solve your problem, you must
reinitialize.

In order to [re]initialize the cryptographic infrastructure do the following:
1. Copy the .nfk file to NICIFK
2. Bring down the server
3. Copy DOMXENG.XLM to NOVXENG.XLM
4. Restart the server.

I've done this with several .nfk files with the same results: the NICIFK
file is still in the SYSTEM folder (not consumed), the manually deleted
files in SYSTEM\NICI are recreated, but no _NETWARE\XMGRCFG.DA0
file is created.

Delaying the loading of the HTTPSTK.NLM module doesn't help. It's
still intermittent.

I'm stumped.


>>> Anders Gustafsson<[email protected]> 2009-04-25 1:59 AM >>>
Steve Conrad,
> I'm testing delaying the load of two modules, in case they're
> loading too quickly:
>
That can also be the case. You can try singlestepping the server
startup with server -KF8

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Let me ask around.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement