Anonymous_User Absent Member.
Absent Member.
692 views

Message: (-9956) DirXMLVerbHandler


hi guys
server 1 :- oes linux 10.2 - edir 20506.07 idm version 3.6.15 edir
driver version 3.6.14 imanager 2.7.3
add server 2 :- oes linux 11.1 - edir 20705 idm 4.02 imanager 2.7.6
if i restart the edir driver while still on environment 1 but using
imanager in environment 2 then in dstrace in environment 1 returns:-

DirXML Log Event -------------------
Status: Error
Message: (-9956) DirXMLVerbHandler::construct: An error occurred while
constructing an object: failed, invalid request (-641).

doesnt affect dirxml events - but i dont like the look of any errors
that i dont understand.
all i can find is "this error occurs when an NDAP request us being
handled by the dxevent module" -
has anyone seen this error before or diganosed it or any ideas how to go
about diagnosing it? - i've tried all the settings in dstrace and
updated all imanager plugins on server 2.
theres nothing wrong with comms between servers or any other errors in
the tree.
rgds
mike


--
zzalsmre
------------------------------------------------------------------------
zzalsmre's Profile: https://forums.netiq.com/member.php?userid=390
View this thread: https://forums.netiq.com/showthread.php?t=49426

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

Re: Message: (-9956) DirXMLVerbHandler

zzalsmre wrote:

>
> hi guys
> server 1 :- oes linux 10.2 - edir 20506.07 idm version 3.6.15 edir
> driver version 3.6.14 imanager 2.7.3
> add server 2 :- oes linux 11.1 - edir 20705 idm 4.02 imanager 2.7.6
> if i restart the edir driver while still on environment 1 but using
> imanager in environment 2 then in dstrace in environment 1 returns:-
>
> DirXML Log Event -------------------
> Status: Error
> Message: (-9956) DirXMLVerbHandler::construct: An error occurred while
> constructing an object: failed, invalid request (-641).
>
> doesnt affect dirxml events - but i dont like the look of any errors
> that i dont understand.
> all i can find is "this error occurs when an NDAP request us being
> handled by the dxevent module" -
> has anyone seen this error before or diganosed it or any ideas how to
> go about diagnosing it? - i've tried all the settings in dstrace and
> updated all imanager plugins on server 2.
> theres nothing wrong with comms between servers or any other errors in
> the tree.


This type of error has been seen previously.

https://forums.netiq.com/showthread.php?47078-PasswordSync-status-shows-error-641

What version of the IDM iManager plugins do you have?

From what I understood, there are issues when performing operations
against IDM 3.6.1 server using iManager IDM 4.0.x plugins.

The issue will disappear once you decommission the 3.6.1 server (there
was a version of the IDM 4 iManager plugins that fixed this also, but
it might require a SR to obtain - not sure if it was ever publicly
released)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Message: (-9956) DirXMLVerbHandler


thanks alex
i'll put in an SR see if i can find out more re: the unreleased
plugins.
its imanager 2.7.6 with all the 4.02 plugins and as you say the error
occurs when operating against the 3.6.1 engine.
i'm was just surprised as they advertise the whole 4.02 thing as
backward compatible.
is it possible/ is there a procedure to downgrade the plugins to 3.6.1
while operating from the later imanager 2.7.6? sounds unlikely/ likely
to break?
cheers
mike


--
zzalsmre
------------------------------------------------------------------------
zzalsmre's Profile: https://forums.netiq.com/member.php?userid=390
View this thread: https://forums.netiq.com/showthread.php?t=49426

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Message: (-9956) DirXMLVerbHandler

zzalsmre wrote:

>
> thanks alex
> i'll put in an SR see if i can find out more re: the unreleased
> plugins.
> its imanager 2.7.6 with all the 4.02 plugins and as you say the error
> occurs when operating against the 3.6.1 engine.


What exact date/build are your IDM plugins? For example a version built
today would have a build number like this: 20131211_123456

> i'm was just surprised as they advertise the whole 4.02 thing as
> backward compatible.


It is (with some caveats).

> is it possible/ is there a procedure to downgrade the plugins to 3.6.1
> while operating from the later imanager 2.7.6? sounds unlikely/ likely
> to break?


Is this more than a cosmetic issue for you?
It will go away when you drop the 3.6.1 box from your driverset.
I'd not bother with trying to downgrade, my advice is to get a fix via
a SR.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Message: (-9956) DirXMLVerbHandler

Alex McHugh wrote:

> zzalsmre wrote:
>
> >
> > thanks alex
> > i'll put in an SR see if i can find out more re: the unreleased
> > plugins.
> > its imanager 2.7.6 with all the 4.02 plugins and as you say the
> > error occurs when operating against the 3.6.1 engine.

>
> What exact date/build are your IDM plugins? For example a version
> built today would have a build number like this: 20131211_123456
>
> > i'm was just surprised as they advertise the whole 4.02 thing as
> > backward compatible.

>
> It is (with some caveats).



Okay, I've confirmed with NetIQ that the a fix for the bug I was
thinking of has been shipped as part of a public patch, so if you are
fully updated you should have this fix.

That you still have errors suggests that there might have been another
similar issue which wasn't fixed.

If it's important to you - raise a SR to get this troubleshooted/fixed.
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.