Discussion Locked

NETWARE SFT 3 SERVER INSTALLED - CANNOT

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

I HAVE INSTALLED SFT 3 4.2 TO TWO SERVERS THAT ARE MIRRORING 24 HOURS VIA MSL...PRIMARY SERVER AND SECONDARY...ALL DONE.

PROBLEM: AT THE SERVER CONSOLE I TYPE IN "LOAD RSPX" AND THE SERVER RETURNS THE ERROR MESSAGE ...CANNOT FIND PUBLIC SYMBOL WITH A PATH TO FILES REQUIRED.

IF I TRY "LOAD REMOTE REMOTE" I RECEIVE THE SAME MESSAGE.

?? AM I MISSING ANY MODULES OR ARE THE COMMANDS DIFFERENT FOR SFT 3 SERVERS?

PLEASE HELP

MERVIN

6 replies

by kuiphoff

Could be a number of things. You haven't included the name(s) of the public symbol(s) so it is impossible to determine where your problem lies.

The error message "Loader cannot find public symbol" is generated when a dependent NLM is not loaded before the current NLM attempts to load OR a mismatched (too new or too old) NLM is loaded.

Novell has provided TID 10014856 to help debug "Public Symbol" error messages.

by kuiphoff

mervin@etsecurity.co.za responded
*************************
Hi there,

Ok these are the erro messages that the server returns:

Server - 4.11 - 1586 Loader cannot find public symbol IncrementScreenActiveCount
Server - 4.11 - 1586 Loader cannot find public symbol GetPreviousScreen
Server - 4.11 - 1586 Loader cannot find public symbol GetNextScreen
Server - 4.11 - 1586 Loader cannot find public symbol DoRealModeInterrupt
Server - 4.11 - 1586 Loader cannot find public symbol DecrementScreenActiveCount

I did check out the TID 10014856 and checked the debugger on another server. All the other symbols except DoRealModeInterrupt refer to an address in SERVER.NLM. DoRealModeInterrupt refers to LOADER.EXE.

Why are these not in memory or are they of the incorrect type or too old?

Please help

Mervin
*************************

If you are receiving these errors you have a problem with NLM revisions. Compare the NLMs and server.exe to whatever service pack you're running to see if t

by kuiphoff

Post Continued....

If you are receiving these errors you have a problem with NLM revisions. Compare the NLMs and server.exe to whatever service pack you're running to see if they were properly updated. Also, compare the NLMs running on this server to one that is working properly to see if that will help you narrow down the problem.

This discussion is closed to new replies.