Anonymous_User Absent Member.
Absent Member.
203 views

IDM 3.5


IDM 3.5 running on a NetWare server, trying to mimic the customer
environment, have not yet patched to 3.5.1 (which is the version that
the customer has), we are trying to start the user migrate from the prod
eDir tree to the vault IDM tree, and we are not seeing any progress,
when looking under IDM Driver Cache inspector we are seeing all of the
sync and modify messages, but none of them has processed.

Further on the DSTRACE screen on the NetWare server we are seeing,

Message: (-9956) DirXMLVerbHandler::construct : An error occurred while
constructing an object: failed, invalid request (-641)

Any thoughts on where the troubleshooting can start? One thought was
updating to 3.5.1 just to see if that might fix something, but not sure
how that would work with the driver still not processing anything.

Thank you,


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=44967

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

Re: IDM 3.5

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

Well, I'd patch to 3.5 SP1 just in case it happens to help. The only
time I remember getting a -9956 was because of a bug in OES where they
did not properly provide symlinks (yes, on Linux, not NetWare) to
jclient* files as covered in TID# 7010129 (the TID was the result) but I
wouldn't expect that to be a problem on NetWare. Patching to 3.5 SP1
may install needed JClient files I guess. Which version of eDirectory
is on here? 3.5.x supported either eDirectory 8.7 or 8.8 on NetWare so
that should be fine either way, but I wonder if this could be a JClient
version issue.

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

iQIcBAEBAgAGBQJQfXvhAAoJEF+XTK08PnB5o9cP/iChSmaMjJSa5Dr2H2FCz5Hv
hUdu4GD+2ln4WUC6R16A8fIlDPsJEosbSMG6rDxtssyQBxevQEgpjCBMpeyLUdkm
kI71mpon/FsqNMxp1+EV44VwnXMqK0mq04sVuQZ6YP9nvYPlcPBpG8CLXJc+G7eW
bxxI0hTGHVMIYx1TB9+41ZJWxpfLzTyhxQ9Tcky+BEx0w5/UwGKq5+un8vnP0jz+
hke9Do01B6IR8x4zJXNaFfyPE67GGPxtx4TQ2KPxXAN9IEM2cSeuh+CuCtAUcLG+
8CDAgGmjZHndd6ckxXDCN9K2xj8j8zb4pl/YeU2TwUpq1tJcj/XcwMu/bJO+joFu
rXeGNv1y0Tp4Vj8wczrKYm9pXLsS+lQguGIjiCWbyyl51EdXEaGb8J13AzFxv4WY
JconoHfYD4C10uVJx9L01XeheMNQ4v/UmopNQSmT8Dqx1C5K/I6RgD+n4RGK9hJM
HqQOIEQD+5PNzcGMaNWW0jSBrObyLlru6TH7Iu59susK00zygHd16o7I307HYReS
8sVzOWbJnldlFVdWEzhDtyF/5iHZvwFBLDxoHHiVig8+CuoqgdLtQ0KNNmqgN8va
7IxPrdN5USHt+YYeQDZwzbVjjb6USRs7zBwcUzH+IZt5s4+Ru1Wmhsf8FeBZYQio
C4l9YhJ4zy5sUzRYZfUu
=7SVT
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IDM 3.5


The plan moving forward is to patch to 3.5.1 and see if that is able to
provide us enough of a testing ground. Have had some additional issues
with making changes to the Vault eDirectory and then that service
crashing. So for now trying to forge ahead and use SLES10SP3/OES2SP3 and
attempt our test again.


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=44967

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IDM 3.5

On Tue, 16 Oct 2012 14:54:01 +0000, dschaldenovell wrote:

> Message: (-9956) DirXMLVerbHandler::construct : An error occurred while
> constructing an object: failed, invalid request (-641)


Trace to file. Set the trace level to 3. Post the trace file to
pastebin.com or some similar service and put the URL here so we can see
what's leading up to this message.


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

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

0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM 3.5

On 10/16/2012 10:54 AM, dschaldenovell wrote:
>
> IDM 3.5 running on a NetWare server, trying to mimic the customer
> environment, have not yet patched to 3.5.1 (which is the version that
> the customer has), we are trying to start the user migrate from the prod
> eDir tree to the vault IDM tree, and we are not seeing any progress,
> when looking under IDM Driver Cache inspector we are seeing all of the
> sync and modify messages, but none of them has processed.
>
> Further on the DSTRACE screen on the NetWare server we are seeing,
>
> Message: (-9956) DirXMLVerbHandler::construct : An error occurred while
> constructing an object: failed, invalid request (-641)



641 is often seen as a error about "You can't do that yet!" Perhaps
trying to do something the engine does not allow. Perhaps trying to
read cache while a driver is running. You can't do that!

Or sometimes when trying to use a new feature of IDM on an older engine.


> Any thoughts on where the troubleshooting can start? One thought was
> updating to 3.5.1 just to see if that might fix something, but not sure
> how that would work with the driver still not processing anything.
>
> Thank you,
>
>


0 Likes
ffreitas Frequent Contributor.
Frequent Contributor.

Re: IDM 3.5

For other platforms TID
http://www.novell.com/support/kb/doc.php?id=7002449 would be what I
recommend, on NW you would have to unload DIRXML.NLM, rename it ,
restart the server, load DSTRACE.NLM, add the +TIME, +TAGS, +MISC,
+DVRS, +DXML tags to it, make it save to a file, rename DIRXML.NLM back
and load it manually. At that point the DSTRACE log (the MISC messages)
will tell you more about the error you are facing as well as other nifty
details on the JVM load.

I hope this is not being caused by a corruption on the DirXML-ServerKeys
attribute, given 3.5.1 is out of support and in that version the only
way to clear the attribute was using DSDUMP.

Good Luck!

Cheers,

-Fernando

On 10/16/2012 8:54 AM, dschaldenovell wrote:
>
> IDM 3.5 running on a NetWare server, trying to mimic the customer
> environment, have not yet patched to 3.5.1 (which is the version that
> the customer has), we are trying to start the user migrate from the prod
> eDir tree to the vault IDM tree, and we are not seeing any progress,
> when looking under IDM Driver Cache inspector we are seeing all of the
> sync and modify messages, but none of them has processed.
>
> Further on the DSTRACE screen on the NetWare server we are seeing,
>
> Message: (-9956) DirXMLVerbHandler::construct : An error occurred while
> constructing an object: failed, invalid request (-641)
>
> Any thoughts on where the troubleshooting can start? One thought was
> updating to 3.5.1 just to see if that might fix something, but not sure
> how that would work with the driver still not processing anything.
>
> Thank you,
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IDM 3.5


We did end up getting the users to move, found out that we had only
created the user names when those users were created, when we added in
the first name, last name those users all were synch'd even created a
new user and that user was moved into the Vault without any issue.

So moving forward we are going to

1.) Update the testing lab to 3.5.1 (to better mimic the environment)
2.) Patch the server (Vault) to SLES10SP3/OES2SP2 (or 3) to provide some
additional stability to eDirectory.
3.) Backup up eDirectory before making any wholesale changes ensuring
that we can "go back" to the starting point so to speak.

Also we were trying to work with the trace files, and I went into both
the driver and the driver set, making sure that logging (trace levels)
were set to 5 and a maximum size of 10 MB, and yet I never saw any log
files being created. Did I miss a step?


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=44967

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IDM 3.5

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

First, skip the DriverSet settings. They're not helpful for real
troubleshooting for various reasons covered in other threads.

Second, did you sepcify a trace file? Below the trace level and above
the max size is the trace file field which, on NetWare, could be
something like sys:/tmp/drivername.trace or something and should then
appear. If you have a sys:/tmp directory I"d probably actually put them
there rather than the root of sys: but it's your call.

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

iQIcBAEBAgAGBQJQf+0WAAoJEF+XTK08PnB5fmYQAJEbTI2RxEvxSnX7EQQ0rmjl
qzRRIR5Dx/wZBdsbMSoWGZ+T++7CGBX8UgdYNpfplr7NE6/zLUH5FuITqDbRCBBt
3jxL8D/uOEUspmDy7E9ozosAy8cNcUSXnXSXC1mC+uMbRRq7NMCD/6oFqDxR9d7s
Y4wxt9wGjom9xlNyWphZaQfp/gU86DneYTCarNaSu+UTwUkTo2KLs/GoC1iTff5y
78suu3UFlK5YmSH86Ms15NFxIx/+VT0WGoUL5dAK7oc45a6wcKXTWTtJWdl8hahn
2MIxWx67g4GYzNAb7LyHviI6wDYhMNQ/Ag7vMFsI85Ce2tjchZp5mhOlefGl26nf
RNyf1NtCO/y8UsVC+wK6gdtXvaBsoyzUJWCwoWJTmERWY2VzgU22DTC1rva99CYR
dMBNGrCbuLzV8eg70n9Byibfz77lte1qfu9+WYBJ9rozfMI15xLKMvqSSA2taBBF
bAgVg5ha/+ZRL/RHyUTfghKM1HofMb5z5yx3iu8Ma443pajYSm7j2CCGABBDh33S
xvpBtrM589PUhj0QyokkGzX1EpURoClSr9T4iaZP+pfwseV7BEo39RqjjKgzNQ79
J3ZRTrMsgAHorQdiDtLoRqJ8NrCsMSxZjsFS9vr1hNZm0FjhHEVmNHN2tkDyePHN
9ONeqFOd4waDTFHAeYB3
=Vu6W
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IDM 3.5


I have the trace level set to 5
trace file sys:/system/idmlogs/driver
10MB is the file size
trace name nwlabtrace

This is set on the eDirectory Driver

This is a small testing environment so should not be on the sys volume
very long since we are planning a migration. But I can certainly
understand not having it on the sys volume since it can hose that up
pretty quickly.


--
dschaldenovell
------------------------------------------------------------------------
dschaldenovell's Profile: https://forums.netiq.com/member.php?userid=205
View this thread: https://forums.netiq.com/showthread.php?t=44967

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: IDM 3.5

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

Okay..... so it generated the file? If not, does that 'idmlogs'
directory exist (it won't create directories for you, though it will
create files if permissions allowed, which doesn't apply on NetWare like
it does on Linux or Unix)? If not, create it and restart your driver
config object (via iManager or Designer) and see if the trace file is,
now, created.

One last thing... I think the slashes work correctly, but if not try
escapes (backslashes) in case those are required instead in the path
leading up to the driver trace file. If that's the case then the system
may have been cleverly creating files named whatever in your DIB
directory. They should stand out if that's the case.

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

iQIcBAEBAgAGBQJQgBYpAAoJEF+XTK08PnB5fkYP/1JA38GoMYgdfnqQhDsStgiw
SKW7WVr2X65koM0uD5eYvXSjzb41eWp0A73JSIyIADABsHu5tnBAHOhCncPWytSb
sj1XcpMwuR4BRnJVLv7VuCS0PgZ8o88eQZ+hleMgNwx51em42qXT8/CSUu/9YeFj
Kw/ahq4NB2epE7NWV2AYNIz3RPQXMUnSHjf2j1rO2Ygufp7fTL6VrMgzV1MNXO5d
yvFiZT3xNX/XYGUrRS03OvM1lGNQ/7zZZwKCRedcOx9pLxkuAdLBzDEcfUP+pfA+
FpFawEAng7AxrMajYawLSsHook5xtQ7iQRN7X2MpN4407tYoBYVDG4lQ1m7TNeDW
0uAKQwD+eLA0xSbefCZWe9zbniEgfIMdQC3ZR3WEScMquPnFUBgQc9Bl8h3vdkZl
M1tfwnXL/KephEVFM5eZSNeC4Wp1tC33hgU9xvbUSLXdvPU5c1k8MDvIa5V9J6ng
7bek2/hsL87eiR7HvXxaRXtMhN1Ni8QWS1EMCx1doNIDK8XfPnIgucg/GIFlZ2P9
NXqPREXzmxlSynHXnEmvU57j1lVKSzhrQe0aINXlxzZQ8bLHkED7edYnExgOYjfk
Zs4KcixgNvAzgVPIi0N3tIo8ZErjAhPb5tjeSvO+vKAR1x6lUHM5w9gL1TXfgEuN
zJfwyp1QETLg3f41Aduu
=gG8d
-----END PGP SIGNATURE-----
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.