NSM 2.0 AD - Problem with Deletes

Brett,
In order to help find out what is happening I will need copy of your
dumpconfig and enginems.txt files from the days that the issue started.
Please send them to storagemanager-at-novell.com.

thanks,
NSM Development

brettking wrote:
> We're testing the deletion of users with only 5 accounts, all of which
> have gone through AD just fine. However only 3 have come through NSM
> but are stuck in "Pending" and I don't see any record of the other two.
> All five folders still exist, the accounts are not used, there's nothing
> in the folders, and NSM has FULL permissions to these folders. The
> "Delete" counters in Engine Status have not changed.
>
>
> PENDING:
> Event Type - 700
> Action - Delete User
> Current Status - Copy data to vault
> Last Attempt Time - 10/14/2009 2:01 PM
> Last Status Change Time - 10/14/2009 2:01 PM
> Next Time Event Eligible - (nothing)
> Last Error - 1
> Object Creation Timestamp - 10/14/2009 1:42 PM
> Event Triggered Timestamp - 10/14/2009 1:42 PM
> Object Deleted - 10/14/2009 1:42 PM
>
>
> ENGINEMS:
> 10/14/2009 13:58:11 3: ALPThread: The event <700> for object <CN=,
> OU....> is not yet delegated; Incrementing try count
> 10/14/2009 13:58:11 4: QueryOK2DelegateTask: Agent <> current copy
> job count = 1.
> 10/14/2009 13:58:11 4: ReportDelegatedTaskDone: Agent <> current copy
> job count = 0.
> 10/14/2009 13:58:11 4: CopyDir RC = 1
>
> EVENT LOGS
> n/a
>
>
> NSM Engine - 2.0.3.9
> NSM Sentinel - 2.0.1.6
> Win 2k3 AD Domain Controller
>
>
> For the life of me, I can't seem to figure out why some accounts work
> with NSM and other do not. This is the same problem with MOVES, as
> well. We tried testing these in an W2k8 AD environment with the latest
> Beta version in both our TEST and DEV environments and the Beta version
> is just having problems all around. I'm about to unload it and go back
> to our "working" 2.0.3.9 version. But I digress.
>
>
> Any reason these three are just sitting there and the other two have
> not even come through?
>
>