Anonymous_User Absent Member.
Absent Member.
509 views

Can't start eDirectory service on windows


There is a server. We installed eDirectory 8.8.6 on windows 2003 R2.
Today I restart SQL server, then the eDirectory services was down.
When I chicked start eDirectory, there was a warning window:
This has been installed as an NT service and is not running. Would you
like to start eDirectory server?
I selected "yes".
There was another warning window:
An unhandled win32 exception occurred in dhost.exe [3952]. Just-In-Time
debugging this exception failed with the following error. No installed
debugger has Just-In-Time debugging enabled. In Visual studio,
Just-In-Time debugging can be enabled from
Tools/Options/Debugging/Just-In-Time.
Check the documentation index for 'Just-in-time debugging, error' for
more information.

How to fix it?


--
tss_swei
------------------------------------------------------------------------
tss_swei's Profile: https://forums.netiq.com/member.php?userid=8349
View this thread: https://forums.netiq.com/showthread.php?t=54075

Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: Can't start eDirectory service on windows

Your best bet to start is to get on a supported platform; windows 2003 is
ancient, and eDirectory 8.8 SP8 is current, so the latter is not supported
by the former:

https://www.netiq.com/documentation/edir88/edirin88/data/a2qqhxm.html

Debugging, as is typical, is not easy on windows. You may be able to look
in the event viewer to see if you can see anything useful, but other than
that I know of no scripts you can debug, no ways to conveniently verify
libraries (from the OS or eDirectory) are in place, etc.

Is this the first server in the tree? Do you have a dev/stage/prod
instance that matches this system which is working? If so, what is
different? Having microsoft sql server on the same box probably does not
matter, unless it is stealing enough resources (RAM, etc.) to prevent
eDirectory from having anything left to use to start; having both on the
same system is probably not a good idea due to resource constraints, but
they do not use the same ports 9by default) so it should not be a conflict.

--
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.