sivaramtm Super Contributor.
Super Contributor.
722 views

eDirectory is not connecting after server reboot

Hi,

We are having IDM 4.6 with eDirectory 9.03 on our windows server. After server reboot eDirectory stopped connecting. Below log got using DHost dstrace service.Please help.


*** NetIQ eDirectory Trace Utility - BEGIN Logging *** fr nov 17 07:04:20 2017
[17-11-2017 07:04:28.91] NMAS : 262147: Create NMAS Session
[17-11-2017 07:04:28.91] NMAS : 262147: Proxy client address [::1]:49263
[17-11-2017 07:04:28.91] NMAS : 262147: Trying local password login shortcut for CN=Admin.OU=sa.O=system
[17-11-2017 07:04:28.91] NMAS : 262147: TCP client network address
[17-11-2017 07:04:28.92] NMAS : 262147: sasUpdateLoginTimeInterval is not set (or) invalid. Setting to global value = 0 mins
[17-11-2017 07:04:28.92] NMAS : 262147: UpdateLoginTimeInterval for object = 0 mins
*** NetIQ eDirectory Trace Utility - END Logging *** fr nov 17 07:05:32 2017

Thanks
Siva ram T
Labels (1)
0 Likes
3 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: eDirectory is not connecting after server reboot

On 11/20/2017 03:24 AM, sivaramtm wrote:
>
> We are having IDM 4.6 with eDirectory 9.03 on our windows server. After
> server reboot eDirectory stopped connecting. Below log got using DHost
> dstrace service.Please help.


eDirectory usually only makes connections to other eDirectory servers, if
applicable, at least out of the box. This does not look like anything
related to that. As a result, I am not sure your description or summary
matches what is happening.

Could you help us understand what you are doing, and how, as well as what
you expect to happen, and what is really happening? Is this connection
being made via LDAP, and if so where is the client involved (outside
eDirectory, a policy within IDM, other?) and when did it work before?

Have you tried logging in as the target user, whatever it is, with some
other method, such as the ndslogin command (on a Linux box in the tree),
or iMonitor (if the user is an admin), or another LDAP client?

--
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
sivaramtm Super Contributor.
Super Contributor.

Re: eDirectory is not connecting after server reboot

We are trying to connect eDirectory using LDAP browser log has been captured at that time. Now with help of Netiq support team we are able to connect to eDirectory after renaming dxevent.dll file. But after renaming this dirxml engine is not loading hence drivers are not starting.

Thanks
Siva ram T
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: eDirectory is not connecting after server reboot

On 11/21/2017 12:24 AM, sivaramtm wrote:
>
> We are trying to connect eDirectory using LDAP browser log has been
> captured at that time. Now with help of Netiq support team we are able
> to connect to eDirectory after renaming dxevent.dll file. But after
> renaming this dirxml engine is not loading hence drivers are not
> starting.


Yes, if you rename the base library which powers Identity Manager (IDM)
then that is likely to break IDM. Hopefully they can get you a permanent fix.

--
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
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.