Highlighted
New Member.
674 views

OES/LDAP vs GW14.2.2

One context in our less than optimal flat tree can not be browsed. What I mean is, I have a GW user, with an invalid or non-existent LDAP association, I click More, Associate and browse to said container, and get this:


*Unable to search LDAP Server
Close
Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 80 - NDS error: cannot go remote (-779)]; remaining name 'o=YTC'

As a work around, I selected the Post office, clicked more, Directory associations. Then entered the context in question, and was able to pick up the non-associated user normally.

Thoughts?
Labels (1)
Tags (1)
0 Likes
6 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: OES/LDAP vs GW14.2.2

In article <tbundy427.83ov2n@no-mx.forums.microfocus.com>, Tbundy427
wrote:
> One context in our less than optimal flat tree can not be browsed. What

...
> Uncategorized exception occured during LDAP processing; nested exception
> is javax.naming.NamingException: [LDAP: error code 80 - NDS error:
> cannot go remote (-779)]; remaining name 'o=YTC'

that error doesn't sound so much like a flat tree error rather than some
actual eDirectory problems. It would be worth running the basic eDir
health check on at least the box you are pointing to for LDAP with the
following commands
ndsrepair -T
ndsrepair -E
ndsrepair -C -Ad -A

If those don't show any problems (if there are, fix them of course) then
either a packet capture of the LDAP look up and/or running the eDir LDAP
trace off of iMonitor is where I'd be looking next.



Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
New Member.

Re: OES/LDAP vs GW14.2.2

ndsrepair -T
ndsrepair -E
ndsrepair -C -Ad -A

These all show everything is OK..

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: OES/LDAP vs GW14.2.2

In article <tbundy427.84gjxb@no-mx.forums.microfocus.com>, Tbundy427
wrote:
> ndsrepair -T
> ndsrepair -E
> ndsrepair -C -Ad -A
>
> These all show everything is OK..


So the over all health is good, but something just isn't flowing
correctly.
What that -779 error Biscay says is that the LDAP server you are
talking to doesn't have the data locally and can't get to it for some
reason.
Yes I've been scratching my head on this, sorry for the delay getting
back to you. All I can think of are some faint ideas, but largely in
the eDir side. Could be something like a filtered replica in there or
an LDAP proxy that doesn't have sufficient rights.
Pointing to a different LDAP server in the tree may make a huge
difference.
I would try using an LDAP browser against each of the different points
you might use to see what differences you see.
The basic JXplorer from http://www.jxplorer.org is what I usually use
for such testing.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: OES/LDAP vs GW14.2.2

Hi,

Further to what Andy has recommended... In the GroupWise Admin Console | System | LDAP Servers --> what LDAP servers do you have defined under your defined Directory? Is there one pointing to a server with a "full" replica of o=YTC ?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
New Member.

Re: OES/LDAP vs GW14.2.2

I ended up submitting a service request. It ended up being a corrupt object. 2 different aliases to the seme user. Neither one were being (or was ever) used! We just deleted both aliases, and it stopped!
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: OES/LDAP vs GW14.2.2

In article <tbundy427.87x1rz@no-mx.forums.microfocus.com>, Tbundy427
wrote:
> I ended up submitting a service request. It ended up being a corrupt
> object. 2 different aliases to the seme user. Neither one were being (or
> was ever) used! We just deleted both aliases, and it stopped!


Thank you for the feedback
this had wondering what was the cause, but like you I think I would have
needed the SR to drill in enough. Now I want to play to see how alias
show in reports such as https://GWserver:9710/gwadmin-
service/list/user.csv


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
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.