Studio Sign In Errors FAQ

Please see below for a short guide on how to overcome the common Studio Sign In errors.

Interactive sign-in is not enabled for this tenant. Enable it from the Orchestrator settings, or connect using the machine key

This errors occurs for tenants created before we introduced the Studio Sign In feature.

Solution

In Orchestrator, go to Tenant > Settings > Security , and then select Allow both user authentication and robot key authentication

image1549×329 24 KB

Interactive connect is not available.

This error occurs because your robot service is installed in service mode which is not yet supported by Studio Sign In feature.

Solution

Re-Installing your Robot in user mode should fix it.

The installers are available on our Automation Cloud Help tab

Click to see the screenshot

image798×926 45.7 KB

Locally unlicensed Studio Enterprise Edition cannot acquire a license from Orchestrator Community Edition. Please use Studio Community Edition.

This error occurs when you try to license your Enterprise installation (MSI) via our Community Cloud Orchestrator account.

Solution

You can either:

• try to connect to Enterprise Cloud Orchestrator account
• install Studio Community Edition from the EXE installer

The installers are available on our Automation Cloud Help tab

Click to see the screenshot

image798×926 45.7 KB

Robot does not exist

This happens because your robot is already connected with a machine key, with robot user defined in Orchestrator using the classic method or via the windows user. When you then sign in in Studio, a different username is sent to Orchestrator

Solution

You can either:

• connect using the machine key (you would want to log out first from Assistant)
• remove the old configuration and retry the Sign In

No robot configured for the current user.

There is no valid license allocated for your signed in user (either directly or via Orchestrator group).

Solution

You should configure your user robots under Tenant → Users and also make sure that there are spare licenses that can be allocated in your Orchestrator.
Sample configuration could look like this (you should be able to leave the Domain\Username empty, it will be auto-populated)

image1001×612 35.4 KB

Please refer to our documentation for further information:

2 posts - 2 participants

Read full topic