• State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 62 subscribers
  • Views 4921 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

onPostRename Started when unlocking AD Account

micha.becker
over 6 years ago

Hi, I've installed the new ARS 7.0.3.2320 version, old version is 6.7.0. I am using the exact same scripts for the new version.

When I am now unlock a locked account over ARS web, the event viewer on the ARS server shows:

operation: modification on object, Attributes :edsaAccountLockedOut False.
next task --> Policy: onPreModify started --> should be OK I assume
next task --> Policy: onPreModify ended --> should be also OK I assume, operation should be finished now.
next task --> Policy: onPostRename started --> WHY??????
next task --> Operation, which should only run when renaming the account
next task --> Policy: onPreModify started --> ARS web is freezing and looping through above steps until Error: The 'Script Execution' policy encountered an error when running the script 'User-Management'. User-Management(986, 9) : Error 0x80131600

So, I really don't understand why ARS is starting the onPostRename when unlocking an account. 

I would really appreciate it if someone could point me in the right direction to solve this issue.

Regards,
Micha

Parents
  • 0 over 6 years ago
    I tested in my lab, and I'm not getting an onPostRename event when unlocking an account.

    This suggests that there may be a custom Workflow or policy script which is performing a rename operation and triggering the event.

    If there is a test Organizational Unit where you can reproduce this issue, I suggest disabling the Policies linked to that Organizational Unit one at a time. Trigger the event, and check the logs to see if the onPostRename occurs. If it does not, re-enable the Policy and move on to the next one. If none of the Policies are causing the issue, do the same with your Workflows. Once you determine which Policy or Workflow is causing the event, you'll be in a much better spot.
Reply
  • 0 over 6 years ago
    I tested in my lab, and I'm not getting an onPostRename event when unlocking an account.

    This suggests that there may be a custom Workflow or policy script which is performing a rename operation and triggering the event.

    If there is a test Organizational Unit where you can reproduce this issue, I suggest disabling the Policies linked to that Organizational Unit one at a time. Trigger the event, and check the logs to see if the onPostRename occurs. If it does not, re-enable the Policy and move on to the next one. If none of the Policies are causing the issue, do the same with your Workflows. Once you determine which Policy or Workflow is causing the event, you'll be in a much better spot.
Children
No Data