
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I have setup a password expiration notification job in iManager on the driver set, and it runs fine. I am testing in QA and have setup the trace and I know it should be finding at least one user that I have configured for the job to find (I confirmed this by running the same ldap query in my ldap browser), but yet the trace only shows the following. Will the job trace 'not' show the users it found?
[01/21/20 15:53:55.794]:Detect users whose password will soon expire JT:: Check Password Expiration Job, version 4.5.0.0
[01/21/20 15:53:55.795]:Detect users whose password will soon expire JT:: Checking configuration...
[01/21/20 15:53:55.817]:Detect users whose password will soon expire JT:: Beginning execution...
[01/21/20 15:53:55.818]:Detect users whose password will soon expire JT:: LDAP search parameters:
base: ou=blah,o=blah
filter: (&(objectClass=inetOrgPerson)(&(passwordExpirationTime>=20200220050000Z)(passwordExpirationTime<=20200221050000Z)))
attrs: mail passwordExpirationTime cn
[01/21/20 15:53:56.953]:Detect users whose password will soon expire JT:
Job Final result -------------------
Job: \blah\blah\blah\blahNotification
Status: Success
[01/21/20 15:53:56.953]:Detect users whose password will soon expire JT:Worker thread for job '\blah\blah\blah\blahNotification' exiting.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Discovered that the account I was running the job as, did not have necessary eDirectory rights to query the attributes. I discovered this by running the job as an eDIrectory admin to troubleshoot, and it then found the users I expected it too.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi
It depends on your trace level, but if I remember correctly, it supposes to put found users to nodeset.
For QA environment, you can get good results, if together with DirXML trace, you will enable LDAP trace.
LDAP trace will show all found users in own (human-friendly) way

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I have the trace at a level 5 but it does not show found users. Could you provide any information on the LDAP trace you are referring too please?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Discovered that the account I was running the job as, did not have necessary eDirectory rights to query the attributes. I discovered this by running the job as an eDIrectory admin to troubleshoot, and it then found the users I expected it too.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
LDAP trace: if you use iMonitor for quick troubleshooting, you can enable DS Trace options LDAP and DirXML Drivers together. It will help you to see the exact situation from both ends.