Loader cannot find public symbol: xxxx

Computer: Hardware Netzwerk
1

Hallo!

Beim Start von V_OS2.NAM auf einem NetWare 3.12 Server kriege ich 100 Zeilen mit folgenden Fehlermeldungen:
CONLOG: System console logging started at Sat Jul 2 20:38:47 1901.
CONLOG: Logging system console to sys:etc\console.log.
GATTERMANN02:load v_os2
Loading module V_OS2.NLM
NetWare 386 VRepair OS2 Name Space Support
Version 1.01 December 10, 1990
Loader cannot find public symbol: nameSpaceUnloadSemaphore
Loader cannot find public symbol: nameSpaceSupported
Loader cannot find public symbol: nameSpaceNLMHandle
Loader cannot find public symbol: nameSpaceLoadSemaphore
Loader cannot find public symbol: nameSpaceDescriptionTable
Loader cannot find public symbol: mirrorMismatchTestCompleted
Loader cannot find public symbol: InitializeNameSpaceEntry
Loader cannot find public symbol: GetEntryName
Loader cannot find public symbol: GetBlockParentNumber
Loader cannot find public symbol: FreeThisEntry
Loader cannot find public symbol: DisplayNameSpaceEDError
Loader cannot find public symbol: DisplayNameSpaceDirectoryError
Loader cannot find public symbol: DisplayError
Loader cannot find public symbol: DisplayEDError
Loader cannot find public symbol: DetermineDirectoryEntryType
Loader cannot find public symbol: deletedBlockTable
Loader cannot find public symbol: CompareNameSpaceEntryNames
Loader cannot find public symbol: ClaimExtendedDirectoryEntries
Loader cannot find public symbol: CheckNameSpaceLinks
Loader cannot find public symbol: CheckIfNameIsUnique
Loader cannot find public symbol: CheckExtendedDirectoryBitMap
Load file referenced undefined public variable.
Module V_OS2.NLM NOT loaded

Ich habe die aktuellen Patches geladen, dazu die neue C-LIB. Was kann ich dagegen tun?

Ich kann mein Volume SYS deswegen nicht reparieren!

tks!
Herbert

2

Das sagt die Knowledgebase dazu.

Gruß
Stefan

Symptom
Customer was trying to run a vrepair on the SYS: volume. He had OS2 namespace loaded on it. Vrepair was unable to load v_os2.nlm. When he exited out of vrepair and tried to load it manually, he got public symbol errors.

Cause
V_os2.nlm, v_mac.nlm, v_nfs.nlm, and v_long.nlm (NW 4.11) can only be loaded by vrepair. If you attempt to load them manually without letting vrepair autoload them, you will get public symbol errors.

These also must be loaded from the same directory as vrepair.nlm. If vrepair will not load them, you can add a search path to your server boot directory.
Examples:
search add c:\nwserver
search add c:\server.312

This will allow vrepair to autoload them from the DOS partition even when the SYS volume is dismounted.

Solutions
Before loading Vrepair, add a search path to the server’s boot directory so that it can autoload v_os2.nlm.

[Bei dieser Antwort wurde das Vollzitat nachträglich automatisiert entfernt]