Highlighted
Super Contributor.
Super Contributor.
374 views

GroupWise Rest Driver: Code(-9006) The driver returned a "retry" status

Hi All

I have been trying to create GW accounts via IDM without success.

 

I ran a trace and found this error on the GW Rest Driver:

Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: <code></code>
<description>Move for DN \TREE\xxx\xxx\xxx still not complete. Will re-try</description>

<operation-data AccountTracking-AppAccountStatus="-" AccountTracking-IdvAccountStatus="-" AccountTracking-Operation="move"/>

 

THE DN was moved a month ago, and it has been stuck in a loop since then. Anyone know how a can forcefully move the DN or fix the issue?

 

The Driver also has a lot of unprocessed transaction, with last processed transaction was last week.

 

Labels (2)
7 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Hi!

I recall seeing similar things before. What has been the problem is that a move of the users mailbox is initiated between post offices in Groupwise, and this process has not finished.

So in order to get IDM to process the next change, investigate the move of mailbox between PO's and resolve that issue. Once resolved, the driver should process the next change.

This is based on what I recall from similar situations before, your problem could of course be completely different. 🙂

Best regards

Marcus

Highlighted
Super Contributor.
Super Contributor.

Thanks for replying.
A move of the user was initiated in the IDM. I checked user object on GW and it is reflecting the new location. The User object was moved to a new location and an alias was created in the old location.



Further investigation on the trace revealed the following:

<product build="20180222_0550" instance="GroupWise REST Driver" version="4.0.0.4">DirXML Driver for GroupWise</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status code="**ERROR** Event-id gw110579 status = warning; " event-id="IDM#20200812150656#4#2:2480487e-8028-47ab-95c0-7e4880242880" level="error" type="app-general">
<code>**ERROR** Event-id gw110579 status = warning; </code>
<description>Error publishing data to eDirectory</description>
<object-dn>\TREE\xxx\xxx\xx\xxx</object-dn>
</status>
<status event-id="IDM#20200812150656#4#2:2480487e-8028-47ab-95c0-7e4880242880" level="success"/>
</output>
</nds>

Highlighted
Super Contributor.
Super Contributor.

Im also seeing the below in the trace:

GroupWise REST Driver PT:Applying policy: NOVLGRPWRAEN-otp-EntitlementImpl.
GroupWise REST Driver PT: Applying to status #1.
GroupWise REST Driver PT: Evaluating selection criteria for rule 'strip "Login Disabled" if expire-account available'.
GroupWise REST Driver PT: (if-op-property 'expire-account' available) = FALSE.
GroupWise REST Driver PT: Rule rejected.
GroupWise REST Driver PT: Evaluating selection criteria for rule 'Intercept outbound queries for gwDomain'.
GroupWise REST Driver PT: (if-class-name equal "gwDomain") = FALSE.
GroupWise REST Driver PT: Rule rejected.
GroupWise REST Driver PT:Policy returned:
GroupWise REST Driver PT:

<status event-id="gw110579" level="warning">Code(-8015) Operation vetoed by filter.<operation-data AccountTracking-AppAccountStatus="-" AccountTracking-IdvAccountStatus="-"/>

GroupWise REST Driver PT: Pumping XDS to eDirectory.

GroupWise REST Driver PT: Performing operation query for .

GroupWise REST Driver PT: --JCLNT-- \TREE\xxxx\idm\Driver Set\GroupWise REST Driver - Publisher : Duplicating : context = 1810825301, tempContext = 1810825352

GroupWise REST Driver PT: --JCLNT-- \STREE\*****\idm\Driver Set\GroupWise REST Driver - Publisher : Calling free on tempContext = 1810825352

GroupWise REST Driver PT: Query from policy result

GroupWise REST Driver PT:

 


GroupWise REST Driver PT: Applying to modify-association #1.
GroupWise REST Driver PT: Evaluating selection criteria for rule 'AccountTracking - disregard if disabled'.
GroupWise REST Driver PT: (if-global-variable 'drv.acctTrk.enable' not-equal "true") = FALSE.
GroupWise REST Driver PT: Rule rejected.
GroupWise REST Driver PT: Evaluating selection criteria for rule 'AccountTracking - assign associations and CN to Local variables'.
GroupWise REST Driver PT: (if-operation equal "modify-association") = TRUE.
GroupWise REST Driver PT: Rule selected.
GroupWise REST Driver PT: Applying rule 'AccountTracking - assign associations and CN to Local variables'.
GroupWise REST Driver PT: Action: do-set-local-variable("oldAssociationValue",scope="driver",token-xpath("./association/text()")).
GroupWise REST Driver PT: arg-string(token-xpath("./association/text()"))
GroupWise REST Driver PT: token-xpath("./association/text()")
GroupWise REST Driver PT: Token Value: "domain.poa.username{106}{AA3DC510-0DD5-0000-AAFB-B3CDD723EB80}0D44BED0-03D0-0000-A34A-B800D600440
0".
GroupWise REST Driver PT: Arg Value: "domain.poa.username{106}{AA3DC510-0DD5-0000-AAFB-B3CDD723EB80}0D44BED0-03D0-0000-A34A-B800D6004400".
GroupWise REST Driver PT: Action: do-set-local-variable("newAssociationValue",scope="policy",token-xpath("./association[last()]/text()")).
GroupWise REST Driver PT: arg-string(token-xpath("./association[last()]/text()"))
GroupWise REST Driver PT: token-xpath("./association[last()]/text()")
GroupWise REST Driver PT: Token Value: "domain.poa.username{106}{AA3DC510-0DD5-0000-AAFB-B3CDD723EB80}0D44BED0-03D0-0000-A34A-B800D600440
0".
GroupWise REST Driver PT: Arg Value: "domain.poa.username{106}{AA3DC510-0DD5-0000-AAFB-B3CDD723EB80}0D44BED0-03D0-0000-A34A-B800D6004400".
GroupWise REST Driver PT: Action: do-if().
GroupWise REST Driver PT: Evaluating conditions.
GroupWise REST Driver PT: (if-xpath true "string-length($newAssociationValue)>0") = TRUE.
GroupWise REST Driver PT: (if-xpath true "contains($newAssociationValue, "106")") = TRUE.
GroupWise REST Driver PT: Performing if actions.
GroupWise REST Driver PT: Action: do-set-local-variable("VarUsrObj",scope="policy",arg-node-set(token-query(class-name="User",datastore="src",scope=
"entry",arg-association("$newAssociationValue$"),"50073"))).
GroupWise REST Driver PT: arg-node-set(token-query(class-name="User",datastore="src",scope="entry",arg-association("$newAssociationValue$"),"50073
"))
GroupWise REST Driver PT: token-query(class-name="User",datastore="src",scope="entry",arg-association("$newAssociationValue$"),"50073")
GroupWise REST Driver PT: arg-association("$newAssociationValue$")
GroupWise REST Driver PT: token-text("$newAssociationValue$")
GroupWise REST Driver PT: Expanded variable reference '$newAssociationValue$' to 'domain.poa.username{106}{AA3DC510-0DD5-0000-AAF
B-B3CDD723EB80}0D44BED0-03D0-0000-A34A-B800D6004400'.

Highlighted
Outstanding Contributor.
Outstanding Contributor.

It is a bit difficult to know without a full level 3 trace of the event (sensitive information removed of course).

But if you look in Groupwise under System and User Move Status, does this user have a Last Move Status of Move completed?

Best regards

Marcus

Highlighted
Super Contributor.
Super Contributor.

Yes, the last move status is complete.
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Ok, I guess a full trace would reveal the issue, but what you can do is to remove the offending transaction from the cache to make the driver process the next change. To do this, use iManager and stop the driver. Then go into the driver cache inspector and remove the offending transaction from the cache. Then start the driver again.

This will not resolve the issue per se, but your driver will then process the queued events if you need to prioritize your other events due to business needs.

If you have more time on your hands, see if you can sanitize and post a level 3 trace of the entire event in like pastebin.org or something.

Best regards

Marcus

Highlighted
Super Contributor.
Super Contributor.

Here is the full level 3 trace below:
https://pastebin.com/E95h1ZTV

The issue seems to occur when a user is moved from one container to another on IDM.
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.