Cadet 1st Class
Cadet 1st Class
1181 views

EMBOX load unresolved

I have a 6.5.8 small business server which as a result of several calamaties, had to be rebuilt from a down server. As a result, edirectory was upgraded from 8.7.3 to 8.8.4 (after patching w/ sp8). No post sp8 patches have been installed.

When booting, embox is unresolved with 3 unresolved symbols.

Here is the logger screen when embox attempts to load.

Loading module EMBOX.NLM
eDirectory Management Tool Box Engine
Version 10554.29 May 15, 2007
Copyright 2001-2007 Novell, Inc. All rights reserved. Patents Pending.
SERVER-5.70-918: Loader cannot find public symbol: XIS11@?bridgeXisRIOStream_wri
te%%YAXPAVXisObject%%J%Z for module EMBOX.NLM
SERVER-5.70-918: Loader cannot find public symbol: XIS11@?bridgeXisRIOStream_rea
dInt%%YAJPAVXisObject%%%Z for module EMBOX.NLM
SERVER-5.70-918: Loader cannot find public symbol: XIS11@?bridgeXisRDOMElement_g
etInteger%%YAJPAVXisObject%%%Z for module EMBOX.NLM
Error processing External Records.
Module EMBOX.NLM NOT loaded
Module EMBOX.NLM load status UNRESOLVED

Additionally, the products.dat file shows embox as version 87.3.0 and ldap as 87.3.9, while edirectory and ndsb are both 8.8.4.

I believe the embox.nlm module which is attempting to load is an 8.7.3 version. The module of XIS11 is v 1.00.03, dated Sep 30, 2008. I believe this to be an 8.8.4 version.

Nldap.nlm is loaded on the system and appears to be an 8.8.4 version, even though the products.dat file shows it to be version 87.3.9. It is version v20217.05 dated 11/11/08.

How can I resolve this issue? I can see 3 possibilities, 1)deleting the products & reinstalling them, 2) leaving them as version 87.3.x in the products.dat file and just putting in a new embox.nlm or 3) putting in the post sp8 patches which may resolve the issue by overlaying the current nlm’s?

Any assistance would be greatly appreciated.
Labels (1)
0 Likes
2 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

flakestar;2296238 wrote:
I have a 6.5.8 small business server which as a result of several calamaties, had to be rebuilt from a down server. As a result, edirectory was upgraded from 8.7.3 to 8.8.4 (after patching w/ sp8). No post sp8 patches have been installed.

When booting, embox is unresolved with 3 unresolved symbols.

Here is the logger screen when embox attempts to load.

Loading module EMBOX.NLM
eDirectory Management Tool Box Engine
Version 10554.29 May 15, 2007
Copyright 2001-2007 Novell, Inc. All rights reserved. Patents Pending.
SERVER-5.70-918: Loader cannot find public symbol: XIS11@?bridgeXisRIOStream_wri
te%%YAXPAVXisObject%%J%Z for module EMBOX.NLM
SERVER-5.70-918: Loader cannot find public symbol: XIS11@?bridgeXisRIOStream_rea
dInt%%YAJPAVXisObject%%%Z for module EMBOX.NLM
SERVER-5.70-918: Loader cannot find public symbol: XIS11@?bridgeXisRDOMElement_g
etInteger%%YAJPAVXisObject%%%Z for module EMBOX.NLM
Error processing External Records.
Module EMBOX.NLM NOT loaded
Module EMBOX.NLM load status UNRESOLVED

Additionally, the products.dat file shows embox as version 87.3.0 and ldap as 87.3.9, while edirectory and ndsb are both 8.8.4.

I believe the embox.nlm module which is attempting to load is an 8.7.3 version. The module of XIS11 is v 1.00.03, dated Sep 30, 2008. I believe this to be an 8.8.4 version.

Nldap.nlm is loaded on the system and appears to be an 8.8.4 version, even though the products.dat file shows it to be version 87.3.9. It is version v20217.05 dated 11/11/08.

How can I resolve this issue? I can see 3 possibilities, 1)deleting the products & reinstalling them, 2) leaving them as version 87.3.x in the products.dat file and just putting in a new embox.nlm or 3) putting in the post sp8 patches which may resolve the issue by overlaying the current nlm’s?

Any assistance would be greatly appreciated.


pretty wild mixup here. once you've upgraded to 8.8.5.6 (by installing the 8.8.5 product and patching it with 885ftf6, ntls2051 and nmas 3327) all the relevant stuff will be overwritten with current code. embox should load after 8.8.5, but you should really apply the rest on top.
If you like it: like it.
0 Likes
Absent Member.
Absent Member.

On Tue, 03 Dec 2013 18:26:01 +0000, flakestar wrote:

> Any assistance would be greatly appreciated.


Are you actually using embox for anything?


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.