kuronen Super Contributor.
Super Contributor.
354 views

Identifying the attribute behind 608 error

When a driver wants to add a new object in IDM and there is an attribute that does not conform to the class data of operation it spits me 608 ERR_ILLEGAL_ATTRIBUTE.

I've always had to iterate the attribute in question with various checks and tests which seems very cumbersome way to do it. Do you have any ways to make eDirectory say which is the problematic attribute?
Labels (1)
0 Likes
5 Replies
kuronen Super Contributor.
Super Contributor.

Re: Identifying the attribute behind 608 error

FYI to people with same question: ndstrace with MISC enabled gives the information on what attribute is in question:


Entry <missing entry 0x1abc> has an Illegal Attr Name: .myAttribute.[Attribute Definitions].[Schema Root], failed, illegal attribute (-608)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Identifying the attribute behind 608 error

On 2019-03-26 09:34:02 +0000, kuronen said:

> FYI to people with same question: ndstrace with MISC enabled gives the
> information on what attribute is in question:
>
>
> Code:
> --------------------
>
> Entry <missing entry 0x1abc> has an Illegal Attr Name:
> .myAttribute.[Attribute Definitions].[Schema Root], failed, illegal
> attribute (-608)
>
> --------------------


Thank you for sharing this. -608 is always a pain to troubleshoot.

IMHO eDirectory should return the attribute name in the (LDAP) error.

/Mark

0 Likes
Knowledge Partner
Knowledge Partner

Re: Identifying the attribute behind 608 error

On 3/26/2019 5:34 AM, kuronen wrote:
>
> FYI to people with same question: ndstrace with MISC enabled gives the
> information on what attribute is in question:
>
>
> Code:
> --------------------
>
> Entry <missing entry 0x1abc> has an Illegal Attr Name: .myAttribute.[Attribute Definitions].[Schema Root], failed, illegal attribute (-608)
>
> --------------------


That is mighty handy! They are very painful.

I imagine 609 missing mandatory would be shown here as well (Though
usially only one or two mandatories, so easier to figure out).

613 syntax error would be nice if it reported as well.


0 Likes
Knowledge Partner
Knowledge Partner

Re: Identifying the attribute behind 608 error

Already put "request for extension" for eDirectory a long time ago...
This is one of the strange errors inherited from the LDAP standard: system knows what exactly missed, but didn't tell anybody. (608 ERR_ILLEGAL_ATTRIBUTE.)
0 Likes
kuronen Super Contributor.
Super Contributor.

Re: Identifying the attribute behind 608 error

Reminds me of the unforgettable "unexpected error" in Windows back in the days. That was some informative error message!

Although it has very little in common with this one. Just one misstep in memory lane 🙂
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.