Anonymous_User Absent Member.
Absent Member.
312 views

vrdim module and activation credential issues


I am in the process of transitioning my IDM servers to SLES from
Windows. I've installed my first SLES server, eDir 8.8.7, IDM 4.0.1 and
everything seems normal but I cannot start any drivers. The error in
iManager when attempting to start a driver is:

Unable to start the driver.
com.novell.admin.common.exceptions.UniqueSPIException: (Error -783) The
DirXML Interface Module (VRDIM) is not currently loaded into NetWare or
into DHost.

ndstrace shows the following when loading vrdim:

3344099072 DVRS: [2014/04/01 11:26:56.847] DirXML starting.
3344099072 MISC: [2014/04/01 11:26:56.849] jvmload: Using existing
JavaVM pointer
118646528 DVRS: [2014/04/01 11:26:56.850] DirXML engine thread
starting.
118646528 DVRS: [2014/04/01 11:26:56.956] DirXML Engine activated for
'IDENTITY MANAGER CUSTOMER'.
118646528 DVRS: [2014/04/01 11:26:56.972] ENG ET:
DirXML Log Event -------------------
Status: Error
Message: Code(-9101) DirXML Activation: initialization error:
Code(-9106) DirXML Activation: invalid credential: Code(-9215) 'AE'
activation cannot be applied on 'EVAL' system
118646528 DVRS: [2014/04/01 11:26:56.973] ENG ET:
DirXML Log Event -------------------
Status: Error
Message: Code(-9101) DirXML Activation: initialization error: 9106
(0x2392)
118646528 DVRS: [2014/04/01 11:26:56.973] Error initializing DirXML:
com.novell.nds.dhutil.DSErr: 9106 (0x2392)
at
com.novell.nds.dirxml.engine.act.DirXMLAct.<init>(DirXMLAct.java:310)
at
com.novell.nds.dirxml.engine.act.DirXMLAct.initialize(DirXMLAct.java:141)
at com.novell.nds.dirxml.engine.DirXML.run(DirXML.java:289)
at java.lang.Thread.run(Unknown Source)

118646528 DVRS: [2014/04/01 11:26:56.973] DirXML shutting down...
118646528 DVRS: [2014/04/01 11:26:56.974] DirXML engine thread exiting.
3344099072 DVRS: [2014/04/01 11:26:57.75] DirXML shutting down.

I've verified my activation credentials as being as current as is
available. (AE 4.0X, Integration Module for Tools 3.5X, Integration
Module for Scripting 3.6X). The only other hit I find on this ndstrace
error is another forum post from a few years ago. Has anyone else seen
this and found a solution besides installing IDM 3.6 and upgrading?


--
stober
------------------------------------------------------------------------
stober's Profile: https://forums.netiq.com/member.php?userid=5986
View this thread: https://forums.netiq.com/showthread.php?t=50415

Labels (1)
0 Likes
8 Replies
Knowledge Partner
Knowledge Partner

Re: vrdim module and activation credential issues

On 4/1/2014 11:44 AM, stober wrote:
>
> I am in the process of transitioning my IDM servers to SLES from
> Windows. I've installed my first SLES server, eDir 8.8.7, IDM 4.0.1 and
> everything seems normal but I cannot start any drivers. The error in
> iManager when attempting to start a driver is:
>
> Unable to start the driver.
> com.novell.admin.common.exceptions.UniqueSPIException: (Error -783) The
> DirXML Interface Module (VRDIM) is not currently loaded into NetWare or
> into DHost.
>
> ndstrace shows the following when loading vrdim:
>
> 3344099072 DVRS: [2014/04/01 11:26:56.847] DirXML starting.
> 3344099072 MISC: [2014/04/01 11:26:56.849] jvmload: Using existing
> JavaVM pointer
> 118646528 DVRS: [2014/04/01 11:26:56.850] DirXML engine thread
> starting.
> 118646528 DVRS: [2014/04/01 11:26:56.956] DirXML Engine activated for
> 'IDENTITY MANAGER CUSTOMER'.
> 118646528 DVRS: [2014/04/01 11:26:56.972] ENG ET:
> DirXML Log Event -------------------
> Status: Error
> Message: Code(-9101) DirXML Activation: initialization error:
> Code(-9106) DirXML Activation: invalid credential: Code(-9215) 'AE'
> activation cannot be applied on 'EVAL' system
> 118646528 DVRS: [2014/04/01 11:26:56.973] ENG ET:
> DirXML Log Event -------------------
> Status: Error
> Message: Code(-9101) DirXML Activation: initialization error: 9106
> (0x2392)
> 118646528 DVRS: [2014/04/01 11:26:56.973] Error initializing DirXML:
> com.novell.nds.dhutil.DSErr: 9106 (0x2392)
> at
> com.novell.nds.dirxml.engine.act.DirXMLAct.<init>(DirXMLAct.java:310)
> at
> com.novell.nds.dirxml.engine.act.DirXMLAct.initialize(DirXMLAct.java:141)
> at com.novell.nds.dirxml.engine.DirXML.run(DirXML.java:289)
> at java.lang.Thread.run(Unknown Source)
>
> 118646528 DVRS: [2014/04/01 11:26:56.973] DirXML shutting down...
> 118646528 DVRS: [2014/04/01 11:26:56.974] DirXML engine thread exiting.
> 3344099072 DVRS: [2014/04/01 11:26:57.75] DirXML shutting down.
>
> I've verified my activation credentials as being as current as is
> available. (AE 4.0X, Integration Module for Tools 3.5X, Integration
> Module for Scripting 3.6X). The only other hit I find on this ndstrace
> error is another forum post from a few years ago. Has anyone else seen
> this and found a solution besides installing IDM 3.6 and upgrading?


If I recall correctly, the attribute that stores the difference between
AE, SE, BE, EVAL is a fairly hidden one, that we mere mortals are not
privleged to have access too. (I imagine, since if we did, we would just
go get ourselves free access).

I am pretty sure this was fixed in IDM 4.02 but certainly post 4.0 and
4.01. Do not waste time installing an older version go for the gusto on
4.02 instead.

It is still possible that you might have an issue, in which case, as I
recall the attribute is stored in such a way that I THINK removing the
server from eDir and recreating would be needed to fix it as a mere
mortal. (I am not 100% sure that woudl work, but might).

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues

> It is still possible that you might have an issue, in which case, as I
> recall the attribute is stored in such a way that I THINK removing the
> server from eDir and recreating would be needed to fix it as a mere
> mortal. (I am not 100% sure that woudl work, but might).


Yes, it is stored on the pseudo-server object, which you can view (but not
modify) via iMonitor. Assuming fixing this with the latest 4.0 SP2
install of SE (vs. AE) does not help then you can also open an SR and a
support rep can delete the value from the pseudo-server for you, in case
you really have strong feelings for this particular eDirectory instance.

Regarding the hackability of this, even if we had access to it the next
time AE was started (meaning you had actually installed AE and were trying
to just change licensing for some illegal reason) I believe the engine
will re-set hat value on startup. I have not tested, and maybe this
really is an install-only settings, but for some reason I do not think so.
In the future I would not be surprised if there was a way to modify this
when needed to avoid calling in or reinstalling IDM.

--
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
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues


Thanks. I guess I'll open an SR. My goal is to move everything to SLES,
eDir 8.8.8 and IDM 4.0.2. Everything worked fine on a clean install in
test, but I have this issue in production. I was hoping to move
everything to SLES before upgrading eDir and IDM because upgrading eDir
on Windows has blown up every time I've tried. Would it hurt anything to
install 4.0.2 on this one server and leave the Windows boxes with 4.0.1
for a few weeks?


--
stober
------------------------------------------------------------------------
stober's Profile: https://forums.netiq.com/member.php?userid=5986
View this thread: https://forums.netiq.com/showthread.php?t=50415

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues

On 04/01/2014 12:54 PM, stober wrote:
>
> Thanks. I guess I'll open an SR. My goal is to move everything to SLES,
> eDir 8.8.8 and IDM 4.0.2. Everything worked fine on a clean install in
> test, but I have this issue in production. I was hoping to move
> everything to SLES before upgrading eDir and IDM because upgrading eDir
> on Windows has blown up every time I've tried. Would it hurt anything to
> install 4.0.2 on this one server and leave the Windows boxes with 4.0.1
> for a few weeks?


No, should be fine. There are customers running wider gaps in IDM
versions in the same tree without issues. I thin you're on the right
track, though.

--
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
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues


Thanks for the reassurance. I'll try upgrading to 4.0.2 tomorrow and
report back.


--
stober
------------------------------------------------------------------------
stober's Profile: https://forums.netiq.com/member.php?userid=5986
View this thread: https://forums.netiq.com/showthread.php?t=50415

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues


My bad, eDir is at 8.8.6 and is not supported for IDM 4.0.2. I guess
I'll be opening a SR. I don't want to risk upgrading eDir until it's
moved to SLES. Too many bad experiences trying to upgrade on Windows.
Thank you both.


--
stober
------------------------------------------------------------------------
stober's Profile: https://forums.netiq.com/member.php?userid=5986
View this thread: https://forums.netiq.com/showthread.php?t=50415

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues

For what it's worth, there is a reason so few customer run eDirectory on
windows. The experience there is about as different from the eDirectory
experience on Linux as windows and Linux are, at their low levels,
different. I would not personally patch a windows eDir install without a
decent production outage scheduled, but I'd feel comfortable patching eDir
on any other platform in the middle of the day because of how quick and
reliable it is.

Just my two bits...

--
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
Anonymous_User Absent Member.
Absent Member.

Re: vrdim module and activation credential issues

On Wed, 02 Apr 2014 14:16:16 +0000, ab wrote:

> For what it's worth, there is a reason so few customer run eDirectory on
> windows. The experience there is about as different from the eDirectory
> experience on Linux as windows and Linux are, at their low levels,
> different.


I have both here. They both work. There are some quirks to the Windows
system, but I can't say that it's any more unreliable than any other
supported platform. The performance on Windows isn't as good, due to the
underlying file system performance, but it basically just works.


> I would not personally patch a windows eDir install without
> a decent production outage scheduled, but I'd feel comfortable patching
> eDir on any other platform in the middle of the day because of how quick
> and reliable it is.


I've done both, multiple times. Neither one (Linux, Windows) was really
any big deal. I did the Linux ones during the day, because they're all
clustered resources and I could easily off-line a cluster node, upgrade
it, and on-line the node again without any appreciable loss of service. I
did the Windows ones off hours because they're not clustered, but other
than that I had no problems with the upgrades.


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

Please post questions in the forums. No support provided via email.
If you find this post helpful, please 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.