Error when editing task groups: "Runtime Error ‘35602’ Key is not unique in collection."

When editing the overall Task Groups in MOVEit Automation (Central)’s Admin console interface or while editing members in a specific group, A 35602 error appears, leaving these settings inaccessible.

Sep 27, 2024
Knowledge

Title

URL Name

Runtime-Error-35602-Key-is-not-unique-in-collection

Article Number

000190519

Environment

Product: MOVEit Automation Version: All Supported Versions OS: All Supported Platforms

Question/Problem Description

This error appears when an admin updates the group in Automation (Central)’s interface, but there is something that prevents Automation (Central) from updating the Local Users and Groups section of Computer Management. There appears to be some kind of block on the Automation (Central) software from updating the Local Users and Groups settings for the Windows server itself. Automation (Central) relies on the Local Users and Groups settings to provide permissions for Automation (Central)’s users, so when there are differences between the two, Automation (Central) throws errors like this one.

Runtime Error '35602' Key is not Unique in the Collection

This could also present in the Permissions when double clicking on a group.

Please note, the only real “updates” or changes that admins will make to the Local Users and Groups sections will be the addition of new groups and new users to specific groups, or the removal of users or groups from these settings. The permissions for the groups will be set within the Automation (Central) interface of the Task Groups. For more information, please see this section of the administrator’s guide or the article: How to use task groups and permissions to delegate access to MOVEit Automation

Steps to Reproduce

Clarifying Information

Error Message

Run-time error '35602': Key is not unique in collection List Group Members Command Failed: 2220 The group name could not be found.

Defect Number

Enhancement Number

Cause

Resolution

From a high level, Automation (Central)’s Task Groups need to match what exists in the Local Users and Groups settings. In most cases, administrators will need to remove the changes to users or groups in the Task Groups and in the Automation (Central) interface, and add the changes to users or groups to the Local Users and Groups settings directly in Computer Management. Automation (Central) will reflect the changes made to the Local Users and Groups section.

A common root cause is when the local access groups for MOVEit contain orphaned SID numbers (Security Identifier numbers in Windows) or other identifiers. After removing these, the access groups in Automation Admin show up as expected.

Please note, in some cases, administrator’s added users from within the Automation (Central) interface as Local Users, intending Automation to exactly reflect the AD user for the individual’s account. The Local User will not be the same as the AD user, so for consistency, it is recommended to remove the Local User account and replace the user with their AD account in any Task Groups the Local User appears in.

Workaround

Notes

Keyword Phrase

Last Modified Date

9/27/2024 9:06 PM

Error when editing task groups: "Runtime Error ‘35602’ Key is not unique in collection."

Files(0)

Was this article helpful?

Was this article helpful?

Error when editing task groups: "Runtime Error ‘35602’ Key is not unique in collection."

Information

Related Articles