The account already exists (#1004) error while assigning roles at folder level from Assign Account/Group

Help Orchestrator
1

Getting “The account already exists. (#1004)” error when I try to assign role(s) to the user Account from ‘Assign Account/Group’ at the folder level for my user account (click on Folder → Click on Users → Assign Account/Group).

I have added this user account at Tenant level and it shows in ‘Manage Access’ tab correctly. I also have the user details shown in Accounts & Groups at the administration level, in the users tab.

Additional information → This is for on-premise Orchestrator setup version 2022.4

2

hi @bdevUiP

have you tried with deleting the account and re added again.

or same times this issue will occurs if we use same mail address for different user.

Because, UiPath recommends having a unique and valid email address for each user.

3

Hey Baskar, Thanks for replying. I’m not using any email ID for this user So no chance of being duplicate with any other user. And when i try to delete the account ( so i can try adding it again), i get a message saying “Not found(#1002)” error, even though i see this user account right there.

4

Hi @bdevUiP

have you tried the below thread.

5

@bdevUiP

Welcome to the community

  1. Are you on modern folders?
  2. What specific roles are you trying to assign?
  3. Did you try to assign roles from tenant level?

Cheerd

6

@bdevUiP I Hope, this steps help you solve your issue,

“The account already exists (#1004)” while assigning roles at the folder level in UiPath Orchestrator (version 2022.4) can be frustrating. Here are some troubleshooting steps you can try to resolve this issue:

1. Check for Conflicting Roles:

  • Even though the user might not be directly assigned to the folder, there might be a role assigned at the Tenant level that grants access to the folder indirectly.
    • Go to Manage Access at the Tenant level .
    • Review the roles assigned to the user and see if any of them grant access to the specific folder you’re trying to assign roles to.
    • If there are conflicting roles, try removing the Tenant-level role and then assigning the desired roles directly to the folder.

2. Refresh Permissions:

  • Sometimes, a temporary inconsistency in permissions can cause this error. Try refreshing the permissions by:
    • Logging out of Orchestrator and logging back in.
    • Restarting the Orchestrator service.

3. Verify User Details:

  • Double-check that the username and other user details (like domain) you’re entering for assigning roles in the folder match exactly with the user account information in the Tenant-level “Manage Access” section.
    • Inconsistent details can lead to this error.

4. Clear Browser Cache:

  • In rare cases, a cached version of the user information might be causing issues. Try clearing your browser cache and then accessing Orchestrator again.

5. Orchestrator Logs (For Administrators):

  • If the above steps don’t work, Orchestrator logs might provide more details about the error.
    • If you have administrator access, check the Orchestrator logs for any relevant error messages related to user assignment or permissions.
7

Hi Anil, Thank you. Answering your questions - 1) Yes 2) Administrator and Robot 3) Yes, that works but it doesn’t work from the folder level.

1 Like
8

Hey Baskar…This post helped me deleting the user and now i was able to add them back and able to assign the role as well fine. Thank you.

9

Thank you, Mukesh…These are good troubleshooting steps…I don’t have this issue anymore but i’ll keep the steps for future reference.

10

Hi @bdevUiP

still anything required is that your problem resolved now?

if yes, please mark this is as solution.

Happy Automation!!! cheers.

11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.