Deprecating Classic Folders issue

Help Orchestrator
,
1

I have attempted to migrate processes, assets, queues, users to a Modern folder as I am no longer able to create Queues in a Classic folder meaning I can no longer run one of the projects. All appeared to be ok on the surface, but when I tried to run a project that used the one Queue from Studio in test mode it said no Queue of this name existed. I also tried to run it from Orchestrator in unattended mode and it couldn’t find the unattended robot returning the following error:

“Couldn’t find any user with unattended robot permissions in the current folder. (#1671)”

I appear to be able to assign the machine and user. I can also see the Queue under this folder.

All very odd.

2

@ChrisC

Can you please check Robot account details and it’s permissions.

3

Sorry for slow reply. I was tied up on other things. I will start looking at this now.

4

Under Accounts & Groups I have one robot account which I have given access to all groups on the drop down.

The issue appears when I look to run an Automation. I can assign a machine. I can assign an Account by typing in the name of the Robot account and assign its role as Robot. However when I click Run it comes up with the error:

“Couldn’t find any user with unattended robot permissions in the current folder. (#1671)”

5

@ChrisC Make sure your studio connected to Modern Folder and run the process and check it is still showing the error “No Queue Found”

Capture

6

Check this detailed documentation for the same from UiPath. @ChrisC

7

Ah ok. That looks promising. Will try this morning.

8

Thank you. I will revise my knowledge of robot deployment.

1 Like
10

Well, a much longer story than I had anticipated! I could only see Default as an option in Studio, so logged out thinking this would refresh it. I then found I could not log Studio back in again. I discovered after an hour or so that the Account Group had the license setting of RPA user…this I discovered no longer appears to give access to a Studio Pro…so I changed it to Automation User and that solved the problem of logging back in. Once logged back in the Modern folder appeared in the drop down at the bottom of the Studio screen, so toggled to that and now the automations can be run from Studio and the Agent. Excellent…I will now move onto the Unattended robot to see if this is still a problem. Thank you for the assistance so far!

11

I have now managed to get the automations working from Studio on machine one by logging out and logging back in and selecting the Modern folder rather than the Classic folder…this took quite a while as I needed to change the license type of the local Group from RPA User to Automation User in order to be able to log back in again.

I am now trying to get the Unattended robot to run the same automations on a second machine. I can now do this when initiating from the Agent on the other machine, but I am not able to initiate it from Orchestrator. The job goes into a Pending state and is never assigned.

1 Like
12

Please make sure your machine is connected to the orchestrator and it will show connected and licensed in the UiPath assistant panel.

Please assign the machine and user to the folder from where you are running it. @ChrisC

Check the below thread as well.

13

The Assistant in the system tray on the second machine says it is connected and licensed with a green status indicator, but it is not signed in to Orchestrator.

If I try to sign in to Orchestrator it says it is “unable to retrieve a license. No more developer robots available. Please update your license!” It then sets the status to yellow: signed in and connected but unlicensed.

I assume these are separate issues. The RPA developer license is I assume some issue with licensing that has been created by needing to setup robot accounts for the Modern folders and something has got messed up…quite what I am not at all sure at the moment. I don’t need to use Studio on the other machine, so this is not currently a showstopper although tiresome.

The Unattended robot would appear to be recognised in that when the Assistant is running it shows as connected and licensed. However automations cannot be remotely initiated from Orchestrator yet as they all go into a Pending state.

So, I can get things working on one machine either from within Studio or using the Assistant, but I cannot run them on the other machine in Unattended mode and I also cannot get the other Studio licensed.

I will keep trying.

14

Hey @ChrisC,

You don’t need to sign in using uipath Assistant. If you are able to see the connected licensed status on the assistant.

You have created the dummy user for the unattended robot right? Have you enabled the unattended option for the user in the robot setup?

Also please make sure you assign the the unattended license to the machine as well.

let me give you some screenshots.

image
image1307×407 47.4 KB

This is my user. Click three dots at right as I have mentioned. Go to Robot setup tab.
Enter the username and password (windows credentials of the machine where you want to run the robot) after enabling the unattended option like below.

image
image1305×563 53.4 KB

Go to the machine tab and click on the three dots for your machine like below.

image
image1309×569 45.8 KB

Assign the 1 license to it like below.

image
image1098×280 16.5 KB

I hope this will clear the issue.

Cheers @ChrisC

15

Thank you very much for your detailed reply.

I have checked your screenshots and I had not set up a dummy local user, instead I had set up a Robot Account. So, to mirror your setup I set up a dummy user like the one in your screenshot and this now shows up in exactly the same way as in your Manage Access listing.

image
image1601×412 98.7 KB

I already had the machine set up with 1 unattended license assigned.

Unfortunately, this has not solved the problem. When the Automation is initiated from Orchestrator it still goes into the Pending state. All very mysterious.

1 Like
16

I note that I am not using a machine template, so I will also try and mirror that element of the configuration…

17

Hi @ChrisC,

I don’t think that is the issue.

We can connect on zoom if you want and we can resolve this if you want.

Thanks

18

No, you right this is not the issue. I can pick this up again at 4pm UK time if you can Zoom then otherwise let me know when works for you tomorrow.

19

I appear to have solved the problem with the Unattended Robot. I would like to say I was completely sure how I solved it, but not sure I can be that confident! I think the issue was that because I have both a Classic and a Modern folder I had an Unattended robot license enabled for the same machine in the Classic folder. I disabled it in the Classic folder and then it worked in the Modern folder…I will continue to check how the licensing and account access functionality works to try and make sure I can debug the next issue whenever that occurs.

Anyway for the moment thank you for the help and I will mark it solved.

2 Likes
20

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