• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 96 subscribers
  • Views 2634 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

ADS Group Update from Dynamic Business Role with many members - Check array length and offset.

QOS
over 7 years ago

I created Dynamic Business role to add members based on some data. This works and the Business Roles was added with ~1300 members.

The business role is connected to an AD group. When the job (ADSGroup_Update) started to add the members to the AD group it got frozen with the following error msg:  "Destination array is not long enough to copy all the required data. Check array length and offset."

There is nothing in the error log on the AD side so the job must be frozen in One Identity before it tries to write anything to the AD.

 

Are there any limitations on how many users that can be added in one single job to an AD group? 
Where do i check/modify the "array length and offset" settings?

 

One Identity version: 7.0.2

Parents
  • 0 over 7 years ago
    I think its related to the amount of users that are being added to the AD group in one single job.

    I just tried to modify the dynamic rule to lower down the members to ~30 users, then adding the AD group to the role, this worked fine.
    Also, the AD group is new created and contains no members in Active Directory so the job isn't trying to add/remove members that are already in the AD group in target system.

    I have done similar work before, connecting AD groups to existing System roles with a few hundred of users. This worked fine as well.
Reply
  • 0 over 7 years ago
    I think its related to the amount of users that are being added to the AD group in one single job.

    I just tried to modify the dynamic rule to lower down the members to ~30 users, then adding the AD group to the role, this worked fine.
    Also, the AD group is new created and contains no members in Active Directory so the job isn't trying to add/remove members that are already in the AD group in target system.

    I have done similar work before, connecting AD groups to existing System roles with a few hundred of users. This worked fine as well.
Children
No Data