Anonymous_User Absent Member.
Absent Member.
432 views

Password sync DLLs say 'running' but they're not

I'm upgrading my IDM environment from 3.61 to 4.02. I installed the new
password sync DLLs on all domain controllers, but password sync from AD
to the ID vault is not working. When I look at the Password Sync
control panel applet on the DC that's hosting the AD remote loader, it
shows all six DCs as "running". When I look at the applet on the other
DCs, they all say "installed". Rebooting a DC doesn't change this.

I'm guessing I didn't install the new DLLs correctly. Do I need to
uninstall the PWFILTER.DLL and PSEVENT.DLL from all DCs, reboot them
all, then try again?

Level 5 Remote Loader trace is here: http://pastebin.com/nygHCbmu


Thanks


Labels (1)
0 Likes
20 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I have good news. At least some of your filters are running, and
I'd be willing to bet that they all are since I've never seen that
status mis-represented. So why no password changes? Not positive, but
first things first.

1. Why do you have 'Use SSL' enabled in your driver config? This is
referring to the driver (meaning the shim, within the RL in your case)
connection to the MAD DC. Since your RL is on a DC that's not necessary
and can cause issues. Disable it and restart your driver config and
Remote Loader to see if that helps. It may not though so....

2. My next guess is rights. This shouldn't break on its own, but often
I've seen administrators trying to troubleshoot password sync issues and
giving themselves rights to the HKLM/Software/Novell/PwFilter/data key,
or else the HKLM/Sofware/Novell/PassSync/ key, usually inheritable so
they can see everything. If done incorrectly (as it often is) this
causes problems for the two processes (the one that writes passwords ant
the one that retrieves them) for some reason that I've never fully
understood. An easy way to test is to uninstall the filter from one DC,
delete that machines HKLM/Software/Novell/pwfilter key (and subkeys),
then reboot and reinstall and reboot again. If suddenly it starts
working then rights were probably the problem. Registry rights within
windows are a mess and painful to fix so usually this is easier other
than the whole double-DC-restart stuff. You may be able to get away
with just deleting HKLM/Software/Novell/pwfilter (and subkeys) and
rebooting, then reconfiguring when back up since the filter may still be
loaded (it "loading" is handled in another part of the registry) but I
always forget if that works on the filter side or the RL/driver
'Passsync' side.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQnBDAAAoJEF+XTK08PnB56gAP+wYsyEuCpAvgBwJnp34w1CRp
2GKLbJl97H6POvwBIgOq7yf/2ukKASG11LCZ/25rvDc6cRCtK/KyvnNnUyzK8Zd7
vb1f9j9mX0uZjr9dham7NXauC5uJ5IfsRdbDEC5qLdrBNwdEva8maZ/lTTgM2Tbq
69GBPgwW60kriDCp4I7GYvFufoYZGm8fAF58rTAyKWs/4Wk18j56f7XNRdrdzWts
CJL/nLAuFrdTNDBBU0QzuFalXLSMsnr5EM6gdunFLxS9ehGufkEfwbmbx9yANlhq
r4pxsEqEUP07kjD3TkiKK7uWaRLKskEIujF+YV4pbWMlyOTfCy07jgM6Ahn3KPDQ
4wwDraT4nWl96M4WbZpLOrkqDnwn1krwfio6B9WN/szOTODqQH7AK45MesB7Rque
vLQ8J1Vfq+mCFl2Qy1FHeIHMgB0JDC6G6N1XHh+5xTHXqum+N9nn25VIpo/UtyFa
W1ndJtwHXlZnEskxK4cQx/TfiOE+A5sPr+F2kpWVoQXVPIUFy85nsmFf1mEApMQg
iGZ+cDmPp3IpWklMaZEtu0raMwB3kn3LYv+6mTuu3lZb8TcGIrW0GjGOUqAIQeJq
/Xh9DEdwTbIo9XMCQch3M7bOTOv/Pn/gm6QwAO9ca86f0UD6Q9omHyGibJqn37tF
GRjsJL2FcLStvssF2EoV
=Qnv+
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

ab ,

> Well, I have good news. At least some of your filters are running, and
> I'd be willing to bet that they all are since I've never seen that
> status mis-represented. So why no password changes? Not positive, but
> first things first.
>
> 1. Why do you have 'Use SSL' enabled in your driver config? This is
> referring to the driver (meaning the shim, within the RL in your case)
> connection to the MAD DC. Since your RL is on a DC that's not necessary
> and can cause issues. Disable it and restart your driver config and
> Remote Loader to see if that helps. It may not though so....
>


So I should have SSL enabled on the remote loader (using the trusted
root cert cert from the ID vault's CA) but not on the driver itself.
Correct?



> 2. My next guess is rights. This shouldn't break on its own, but often
> I've seen administrators trying to troubleshoot password sync issues and
> giving themselves rights to the HKLM/Software/Novell/PwFilter/data key,
> or else the HKLM/Sofware/Novell/PassSync/ key, usually inheritable so
> they can see everything. If done incorrectly (as it often is) this
> causes problems for the two processes (the one that writes passwords ant
> the one that retrieves them) for some reason that I've never fully
> understood. An easy way to test is to uninstall the filter from one DC,
> delete that machines HKLM/Software/Novell/pwfilter key (and subkeys),
> then reboot and reinstall and reboot again. If suddenly it starts
> working then rights were probably the problem. Registry rights within
> windows are a mess and painful to fix so usually this is easier other
> than the whole double-DC-restart stuff. You may be able to get away
> with just deleting HKLM/Software/Novell/pwfilter (and subkeys) and
> rebooting, then reconfiguring when back up since the filter may still be
> loaded (it "loading" is handled in another part of the registry) but I
> always forget if that works on the filter side or the RL/driver
> 'Passsync' side.
>


Password sync worked in both directions before I installed the new DLLs,
and I haven't mucked about with any AD rights since then. I will try
the procedure you suggest anyway, as I can't be 100% certain that our
domain admin hasn't been tinkering with it. It's not likely, since he
knows bupkis about IDM and likes it that way, but ...


Thanks



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not


>
> 1. Why do you have 'Use SSL' enabled in your driver config? This is
> referring to the driver (meaning the shim, within the RL in your case)
> connection to the MAD DC. Since your RL is on a DC that's not necessary
> and can cause issues. Disable it and restart your driver config and
> Remote Loader to see if that helps. It may not though so....
>
> 2. My next guess is rights. This shouldn't break on its own, but often
> I've seen administrators trying to troubleshoot password sync issues and
> giving themselves rights to the HKLM/Software/Novell/PwFilter/data key,
> or else the HKLM/Sofware/Novell/PassSync/ key, usually inheritable so
> they can see everything. If done incorrectly (as it often is) this
> causes problems for the two processes (the one that writes passwords ant
> the one that retrieves them) for some reason that I've never fully
> understood. An easy way to test is to uninstall the filter from one DC,
> delete that machines HKLM/Software/Novell/pwfilter key (and subkeys),
> then reboot and reinstall and reboot again. If suddenly it starts
> working then rights were probably the problem. Registry rights within
> windows are a mess and painful to fix so usually this is easier other
> than the whole double-DC-restart stuff. You may be able to get away
> with just deleting HKLM/Software/Novell/pwfilter (and subkeys) and
> rebooting, then reconfiguring when back up since the filter may still be
> loaded (it "loading" is handled in another part of the registry) but I
> always forget if that works on the filter side or the RL/driver
> 'Passsync' side.
>


Okay, I removed the password filter from one DC. When I attempted to
remove the pwfilter key in the registry, I was told 'access denied' (I
was logged on as a domain administrator). I rebooted, then reinstalled
the pwfilter and rebooted again. Still no good. The password only
propagates to the ID vault if it's issued from the DC that's running the
driver.

Remote loader trace that follows a password change issued from the DC
that's hosting the driver is here: http://pastebin.com/XDCTnJmC (user
ID is 'dbtest2').

Remote loader trace that follows a password change for the same user
issued from the DC where I removed and reinstalled the filter last
night: http://pastebin.com/yHUFLhQc .



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Remote loader trace that follows a password change for the same user
> issued from the DC where I removed and reinstalled the filter last
> night: http://pastebin.com/yHUFLhQc .


Well the good news is that this trace shows that your filter is working
correctly. The bad news is that since you were unable to delete the
key, and also since the password never comes across, you still have
rights problems. Deleting that key should be possible so try again I
guess. Don't use the user which is accessing MAD from IDM since
obviously that one doesn't have enough rights yet. Using
'Administrator' (not just a domain admin, which is less-powerful) may do
it on the DC with the issue. Worst case you can use srvany to create a
service for the sole purpose of loading something like regedit; if you
do this, set it to interact with desktop, and then login to that server
properly and start the service you will have regedit running as SYSTEM
which means nothing can stop you.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQnTCIAAoJEF+XTK08PnB514sQAM5lKxF3SQ46DuE090BVv/KC
BkEyVfKcX8Nm9RVXJzl2BuqBKmKp95CqPKf9hYugdP7F5UfY8HPIfhO6dQvpcSRS
VmBFQ+P7meaiY4NF1zoWQak9i4Uq6oWzKvrhxAcicOods5Nj1BpcUSrbLpV+BODo
lCRUroU87Vl/zBSRF8z4LmwN6VXQZm+jYHO6Xrjr9O0IvrZ6pxCD6oKvCxh5HDss
mcDIGosSDmrr1U7Ut6AyQyfkx9N3wNOcmQPtnnYWp42p8FhSMlNNsAVEDND6HxCo
ADJwvR4Wk5Ya85SPetFTWJGplsWQxA9+RGBFwTGxzoltM7jQp4O43OE1MFziVeIO
ftqWDkUBF1IsP39CRHdgmu3Qxp1VEwycM0lqsNWbUGhTCpKZA33ImByv+PHLYhyt
6yr051GIKMA2D50XKFbWSG9F3WnabEM8VazYmZby0hcpQA477SR+1Da1D7zSWYPQ
n3gsNNG4GYLbW02mH65UDWDqurClEkvDWpzTeA848bFHfGtCC5FaWXglYjL5VHfl
K6sGePrWoEaQ0EA8rfvOAPCuaT2i9bZxngzXDyauhTL97LkBg2Qtt5PjNBwZHef4
xF9AwwcBprqJlvcL7rApS7g6tnxg2rLKIyUO4bjnRFXbQp5ZvXVS0oeAFKoKFYFC
T/R/Cfms8DXqTpLv96N9
=lHVk
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

ab,
>
> Deleting that key should be possible so try again I
> guess. Don't use the user which is accessing MAD from IDM since
> obviously that one doesn't have enough rights yet. Using
> 'Administrator' (not just a domain admin, which is less-powerful) may do
> it on the DC with the issue. Worst case you can use srvany to create a
> service for the sole purpose of loading something like regedit; if you
> do this, set it to interact with desktop, and then login to that server
> properly and start the service you will have regedit running as SYSTEM
> which means nothing can stop you.
>


I'm told that there is no 'Administrator' account (nor any other local
user account) on domain controllers. Our AD admin is going to try
removing the key with his Enterprise Admin account.

Thanks

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

ab,
>
> Well the good news is that this trace shows that your filter is working
> correctly. The bad news is that since you were unable to delete the
> key, and also since the password never comes across, you still have
> rights problems. Deleting that key should be possible so try again I
> guess. Don't use the user which is accessing MAD from IDM since
> obviously that one doesn't have enough rights yet. Using
> 'Administrator' (not just a domain admin, which is less-powerful) may do
> it on the DC with the issue.



Here's the fix our enterprise administrator found.


(do not skip any steps in this)

Right click Novell
Click permissions
Click Advanced
Click Owner
Change ownership to your domain admin account (You will get one
or more errors)
Select the check box “ Replace owner on subcontainers and objects”
Click Apply

Right Click Novell
Click permissions
Click Advanced
Add your admin account to the permissions list (Full Control)
Click Apply (You may get more errors)

Right Click Data
Click permissions
Click Advanced
Add your admin account to the permissions list (Full Control)
Click Apply

Delete keys and reboot

I can't actually reboot until after 10pm, so I won't know until tomorrow
whether this fixes the password sync issue.


Thanks




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

I uninstalled the PWFILTER.DLL, deleted all HKLM/Software registry
entries up to and including 'Novell', rebooted, reinstalled PWFILTER.DLL
and rebooted again. Still no joy.

At this point, I guess the only thing left is to uninstall and reinstall
all password sync components from the DC that's running the driver.
Thoughts?





0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just to be sure, are you testing with the same user for the password
change on both the DC running the RL (which works) and the DC that is
remote? If not, could you to see if that makes a difference? Also, do
you have a trace of a password change from the remote DC on which you
did that reinstall work?

The RL side's registry stuff REALLY shouldn't matter if any single user
works from any DC, unless it is broken for certain users because of
rights on the keys specific to those users.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJQo9ZOAAoJEF+XTK08PnB5UzMQAKXnYEbfy2t5gtzCP0sXgIyu
sHBkjnhSWUWiqGSsUCLotEfUU19uqscOWhheHvSpQT2uCffTXFEc4bJ6UG+Y8Ux5
sq+APZNHv0ys1GyrStBu874dhTiaecspwzei57uUMMBTBcF+9Rd0W51BrSIrvf0V
y6E7sK+JpKGDFECfFo/JEeUIVnHzXTg56QImi+nmD18bSCIHlfnqx9WvJUMM7syS
ekbbt1oraUTDhgSAjvy+nb+FhuFz1TiYeEvMW0PwYr6I0EebJK6uxIjTtNdQyoZ5
4glrtErPHVxMIbOwFlIOmLqprN/nwkkI5NakRAAB7VTg/ZWgdrHh9YJxl10dZP+C
nQbxxW9kJ9MsloowagtV7hHVZfvhXNXiITq/5qDLrJoXc+3X+SRBhdYQQxTudjfN
t9dqxgR1VsBFs7in2BI0HWFxDIBGWcipmCNS1BCZBDDYkkhDjLYtI6MNx17XcMCm
tYfPL5vkb5AaJzKEz1o8/hEvjuXKC7uL4cGFUcJrmOJJOVzCkqFM7IXT1MmJ7Cb5
gbbuuKY2EgQUXfZLmwxfA/euWclVIDGMsqbrGMM+ecaRLRgr0/gvziozoTa7+R2k
wbTzr+MD1ikrhGo7rtmf4XQWN48AvtbCD6VFLXicWgbPNjl4YdDm/DfzAJ9a1W40
0G+GPf4Cj5pa/lYRuy4D
=skEO
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

ab,

>
> Just to be sure, are you testing with the same user for the password
> change on both the DC running the RL (which works) and the DC that is
> remote? If not, could you to see if that makes a difference? Also, do
> you have a trace of a password change from the remote DC on which you
> did that reinstall work?
>
> The RL side's registry stuff REALLY shouldn't matter if any single user
> works from any DC, unless it is broken for certain users because of
> rights on the keys specific to those users.
>


Yes, I've been testing with the same user account every time.
Just for the heck of it, I've created a new account, ssap99, and changed
its password from the DC running the remote loader:
http://pastebin.com/RgZP3aVL, and from the DC on which I reinstalled the
password filter last night: http://pastebin.com/t6rLYmJX .


Thanks


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I guess you are welcome to try reinstalling the password sync
stuff on the machine running the RL, but in my opinion this last set of
test proves, without any doubt, that the problem isn't on that machine.
The trace shows that the remote DC let the RL know about the incoming
password, and then that password was not ever retrieved even though it
looks like it tried to retrieve it. That, to me, means that the driver
could not retrieve it and that is usually because of rights problems
assuming the remote machine can be accessed at all.

Anyway, I'm not good enough at MAD registry stuff to troubleshoot too
much more deeply than that. You could try procmon on the remote DC and
watch the HKLM/Software/Novell key structure to see if anything tries to
poke around in there. If it does, maybe you'll see more details. Also,
I think David sometimes mentions running debugview (or whatever its file
name is) on machines involved in password synchronization since if you
do so you can get more information out of the filters and that may be
interesting. Note: you must be pretty privileged to properly run that
program, obviously.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJQpByQAAoJEF+XTK08PnB5Bj0QAJ2pLzXpOHAzuIcRk8zdLn4x
PR0S4cyr4eOWGjW07zxijhxVe1LFDfDF8GjlY6ke9allrdgiflDp5qdEyaE00qQG
k9IQ6l7mWrL/C5SK//TDkXj4Ctism0R6faQh/DBayMlk5X5pi7LSDLHs8iaG/7aj
EVM4q8HvciZUI3DyHbADcfXaHhVnkFvt+0z3vvDICuVVCzjOrbRTKA6HHFiQtmvs
ciTAalC8Hop/Hx7pajHNmq1E/3+k93SKjfAHbjdExyb/DlGTLxfWDfjcs4VexE/w
0g+OfIlsQiB4zMsD3L93BJwrQYIMgSQLpRwNZ/t/isZH60gv35v7LQOZE3OvJvPS
tVt07i7Szd8RJKa67RHLIxZeSwFWWVVOdngrxA9I+CukCKBlHoLapR+6ljL8hloQ
w/NyXee0GafE0HOUjqAdMZ7DsNcm1bIXhe0kcTn6qsDbHw14THXnFsjLZeVB3Svg
neZRUcSLZhRhpMLnGAcVw9NGqzO9YycIxPZhFfpVotsUFsmMo/6nCJIWf1Y2FsQB
OQUOp0cfx7d/h6Jzg1/bA/gujAnejKeuttwC1X5f5qf07qgcnIaYu/+ntSqAbgR4
FS8JjlpGVezXnYRBjd6r31YhksVh8kZqm7QBC+1DUj5IZPIxhn4JTZfEIGFmqYro
t693clIHmHB+qigJsg37
=7X7C
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not


Sounds like it's time to open a support incident.

Thanks


--
6423241
------------------------------------------------------------------------
6423241's Profile: https://forums.netiq.com/member.php?userid=284
View this thread: https://forums.netiq.com/showthread.php?t=46120

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

On Wed, 14 Nov 2012 22:34:56 +0000, ab wrote:

> Anyway, I'm not good enough at MAD registry stuff to troubleshoot too
> much more deeply than that. You could try procmon on the remote DC and
> watch the HKLM/Software/Novell key structure to see if anything tries to
> poke around in there.


For Registry stuff, RegMon seems a better choice.


> I think David sometimes mentions running debugview (or whatever its file
> name is) on machines involved in password synchronization since if you
> do so you can get more information out of the filters and that may be
> interesting.


Yes. At least in previous version (and I assume the current ones, though
I haven't tested it), the filters are debugview enabled, and put out
messages that you can see to let you know what's going on.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> For Registry stuff, RegMon seems a better choice.


I'm pretty sure procmon is the replacement for both regmon and filemon.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJQpQx9AAoJEF+XTK08PnB5js4P/AwVsmcJnAv7PTaPVKmylJaE
rjHoz20GXF4YLzPIm6cc3vtJ0Pic7LhbA+CfWBf52zQOM6KqkyrTIduhNJISpLBo
gWo0N4jbyE9hkGBCQ60huJNS7TPW2dkMBFoIgziiZQdsTRNEllmVSxzwUPldTPcR
HcSgzq9KU2wQE9DNcXAOj7ikiF8zDzkd6Wn8zBrcSG9Ok+3Q5mV7/G5IvcfA4fm3
RWPEcLT7XrKgkK11ffA0TYl9/RwkSykEB+9WIwMSiGTw311QJ06TXjlXGc8P1mpN
Mq5p927ckjcbRHIKFoq3s93cbxHeL85JxZbJuttB8ACKKdU+zpiWayfP62e//uTZ
HjX7DScKM6zhT2RT7hrn+FLnvWUrIK7h4RveYvnq7AW93Kqq7hAL2KgPKy0thcrX
dNxHqgaV243Ssyww2jTj4hHIQxEtnzJl8GCk4q6Cey6aacAUuq1svb9C0hgbaITo
/7qM1Vb+gwNbaT5FB531LBxh/eI+dUs3c0jAC6RMOSTq0rWQToHHslpJz02pTqX9
4HWHXUjc8DnjE7tME9VLvG5NAOpCy/bbEt3El5mZ/Kr84DzbDd4r4dNV/sPwLfTk
kr03MQKLdzfypeOpGRr7flGBzVQzvXhMSLE0Ow9RA4iOT3LS9VjNnYa7Do8SCps5
8UdppfFVO631MPyNpRYb
=wIpm
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Password sync DLLs say 'running' but they're not

On 14.11.2012 19:40, Douglas Black wrote:
> ab,
>
>>
>> Just to be sure, are you testing with the same user for the password
>> change on both the DC running the RL (which works) and the DC that is
>> remote? If not, could you to see if that makes a difference? Also, do
>> you have a trace of a password change from the remote DC on which you
>> did that reinstall work?
>>
>> The RL side's registry stuff REALLY shouldn't matter if any single user
>> works from any DC, unless it is broken for certain users because of
>> rights on the keys specific to those users.
>>

>
> Yes, I've been testing with the same user account every time.
> Just for the heck of it, I've created a new account, ssap99, and changed
> its password from the DC running the remote loader:
> http://pastebin.com/RgZP3aVL, and from the DC on which I reinstalled the
> password filter last night: http://pastebin.com/t6rLYmJX .


Have you checked firewall connectivity?

There may be something blocking proper RPC between DC-VP04.univ.EDU
(where your driver shim is hosted) and DC-VP03.univ.EDU

[PWD 5640] lpszDCName = DC-VP03.univ.EDU status = 0x000006BA
[PWD 5640] - SetFilterInfo() returned 0x000006BA

where 0x000006BA translates as:

RPC_S_SERVER_UNAVAILABLE
1722 (0x6BA)
The RPC server is unavailable.

See: https://www.netiq.com/support/kb/doc.php?id=3304529 and
https://www.netiq.com/support/kb/doc.php?id=3554990

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.