robert_maury Absent Member.
Absent Member.
348 views

Unable to find extension handler 2.16.840.1.113719.1.14.100


Hello,

When i start my appuser i have this message "Unable to find extension
handler 2.16.840.1.113719.1.14.100 in extension list" on my ndstrace
edirectory server. I don't know the origin of my problem and what i have
to do to resolve it?
i think it lacks me a schema extension but i don't know what kind of
extension

Best regards


--
robert_maury
------------------------------------------------------------------------
robert_maury's Profile: https://forums.netiq.com/member.php?userid=9145
View this thread: https://forums.netiq.com/showthread.php?t=53689

Labels (1)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: Unable to find extension handler 2.16.840.1.113719.1.14.100

The '2.16.840.1.113719.1.14.100' number does not appear to be complete.
Did you copy/paste it?

You may want to get ndstrace output with +TIME +TAGS +LDAP in order to
troubleshoot this further if that is the correct number, but I'm guessing
the number itself is incomplete based on the list of available extensions
on the LDAP Server objects in eDirectory.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
robert_maury Absent Member.
Absent Member.

Re: Unable to find extension handler 2.16.840.1.113719.1.14.100


Hello

Hello,

yes it's a mistake :

I have this message in my trace :

Unable to find extension handler 2.16.840.1.113719.1.14.100.11 in
extension list.

Best regards


--
robert_maury
------------------------------------------------------------------------
robert_maury's Profile: https://forums.netiq.com/member.php?userid=9145
View this thread: https://forums.netiq.com/showthread.php?t=53689

0 Likes
Knowledge Partner
Knowledge Partner

Re: Unable to find extension handler 2.16.840.1.113719.1.14.100

I presume you're asking because the UserApp (worded 'appuser'?) fails to
start, not that it just happens to print out this message. If that is not
the case, knowing as much would be useful information.

Extensions are stored on LDAP Server objects, and thus are specific to
servers doing LDAP stuff in eDirectory. If you have an IDM engine then
certain extensions are added to that object when things (like IDM) are
installed letting the LDAP server/service know that additional extensions
are possible because of modules on that system. These would be provided
by (in your case) the IDM engine.

Is your UserApp pointed to the LDAP system that hosts the appropriate IDM
engine and UserApp driver? If not, then why not? What is the history of
this eDirectory server such that it may not have the extensions added
normally during the installation process?

Pulled from my generic IDM servie I have the following extensionInfo
attribute value which indicates any old IDM engine should have this. If
yours does not, I'm guessing you're pointing to the wrong server:

RSMyLjE2Ljg0MC4xLjExMzcxOS4xLjE0LjEwMC4xMSMyLjE2Ljg0MC4xLjExMzcxOS4xLjE0LjEwMC4xMiNkeGxkYXAA
E#2.16.840.1.113719.1.14.100.11#2.16.840.1.113719.1.14.100.12#dxldap

You can add this to a box using LDAP, but if you do not have the backend
pieces in place (dxldap module in particular) it will probably only cause
problems. I'd probably recommend making sure the engine install worked
properly before doing this:


dn: cn=ldap server - yourserver,dc=container,dc=goes,dc=here
changetype: modify
add: extensionInfo
extensionInfo::
RSMyLjE2Ljg0MC4xLjExMzcxOS4xLjE0LjEwMC4xMSMyLjE2Ljg0MC4xLjExMzcxOS4xLjE0LjEwMC4xMiNkeGxkYXAA


There should only be four lines there.... hopefully it comes through
properly. Again, that's a brute force way to fix something that should be
there, but assumes that the value should be there as mentioned above.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and 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.