On 2018-08-13 17:46, dgersic wrote:
> I had SR # 101165677501 open for a client with this same issue. We ended
> up abandoning the SR as unresolved, but the symptoms sound the same.
> I had it happening with a JDBC driver doing a resync all objects on the
> subscriber. I had it happening with a MAD driver on the publisher
> writing to a (large) object.
> We wandered around the "high value count" thing for a while. IMHO,
> that's not an answer, nor related to this actual issue.
I just created a new text driver that does a XML export and the -626 is
back when exporting thousands of objects. With just a few it works fine.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
We are also now seeing these ALL_REFERRALS_FAILED errors under IDM load now, whereas with eDir 8/IDM 4.5 getting them was a sign of actual issues with the environment. We are not seeing any replication delays, and ndsrepair -E and -T are all clear. I plan to address it with our PSE after the holidays and will post back any findings.
we are also facing exactly the same issue with IDM 47 apps (this error is thrown in catalina.out) and on a loopback driver logs.
Can someone help the root cause of this issue and how this can be resolved.
Thanks in advance.
Leaving here as reference. Saw this at a customer.
Loopback driver handling requests giving Message: Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: Code(-9011) eDirectory returned an error indicating that the operation should be retried later: novell.jclient.JCException: createEntry -626 ERR_ALL_REFERRALS_FAILED<application>DirXML</application>
This particular server was having issues on NCP because of another server's migration and port change from 524 to 1524. As soon as the port was opened, the events resumed.
Support mentioned that when a server goes into a bad address cache, NCP operations will fail which results in other operations not being allowed.