User logged into console. Please log out before trying another multi-user deployment.

​@Matt.Stewart 

​@Marc Mueller 

​@Vatsy 

Do any of you have insight into this?

​@GOAA  Please check auto login setting for RDP Session  - Session lock vs session open 
also could you please confirm that when you singed out  using below procedure ?
Windows button → Right Click → shutdown or Sign out ->Sign out 

HELLO ​@rbkadiyam 

I try with lock sessioni, unlock session and logoff. But doesn’t works

I try with a sesion open and without session open, and doesn’t works

Only works with regular.

​@GOAA  Now I would suggest to clean the profile 
 

Steps: 

• Stop AA Bot agent service in runner/creator machine 
• login into control room → Manage → Devices → Remove the device 
• delete Automation anywhere folder under C:\Windows\System32\config\systemprofile\AppData\Local\
• Start AA Bot agent service 
• connect to Control room to make sure Device connected and showing into the control room

This will clear any open sessions and any cache.

 

HELLO ​@rbkadiyam 

I did that you wrote me.

But, when the session is open works fine (with lock and unlock session), but the problem is when need to create a new session to Exceute a bot.

Hello ​@GOAA , please follow the article below.

https://apeople.automationanywhere.com/s/article/Automation-360-Error-User-logged-into-console-Please-log-out-before-trying-another-multi-user-deployment

Hello ​@Sajith Sudhakaran 

I did that, but didn’t work. All close all sesion, but the RDP fails when needs to create the sesion

I need to work in RDP mode because, i need to control the Screen Resolution.

Thanks!

​@GOAA  try to save this script in .bat file ; place into runner machine - right click and run as adminstrator.  Then run the bot. 

--------------------------------------------------------------RDPSessionOut.bat----------------------

@echo off
setlocal enabledelayedexpansion

for /f "skip=1 tokens=1,2,3" %%a in ('query user') do (
    set "user=%%a"
    set "user=!user:>=!"

    if /i "!user!"=="%USERNAME%" (
        set "sessionID=%%c"
    )
)

if defined sessionID (
    echo Found session: !sessionID!
    tscon !sessionID! /dest:console
) else (
    echo Session not found.
)

endlocal
------------------------------------------------------------------------------------------------------------------

This worked for me with the same scenario that you mentioned.

hello ​@rbkadiyam 

I try with admin mode, but doesn’t work. The rdp session still failing.

​@GOAA  will you be able to provide node manager, Wfree_RDP, AAchromeBotBrowserAgent logs along with the control room → Settings → Device → Auto login settings

hello ​@rbkadiyam 

I attach the logfile.

Only the nodemanager because the another files was empty. Previous execution, i delete all logs.

This file is a part of the log,  and for security reasons, has a lots user o url replaced with xxxxxx

​@GOAA  here are my findings ::
Steps / Actions identified from the Log: 
 

1. Existing RDP Session Already Active

The Node Manager detects an active RDP session:

session name:RDP-Tcp#0 username:YYYYY sessionId:18

It also shows:  number of RDP sessions currently:1

2. AA Tries to Create/Re-use a Session

User has chosen to reuse existing session if available or create a new one if none available.

But then: Could not find an existing session that matches session key

3. Session Creation Fails

Error occurred during bot session creation

Followed by: Unable to perform rdp for the user as we have exceeded the maximum session count

4. Deployment Fails

status_type: DEPLOY_FAILED

--------------------------------------------------------------------------------------------------------------

Most Likely Causes

---------------------------------------------------------------------------------------------------------------------

Cause 1: Windows RDP Session Limit Reached

The bot runner machine already has the maximum number of RDP sessions allowed.

For example:

• Existing user logged in via RDP
• Another disconnected session exists
• Windows Server session limit configured to 1

FIX : Log Off Unused Sessions

On the Bot Runner machine:

query user

Example:

USERNAME     SESSIONNAME   ID  STATE
botuser      rdp-tcp#0     2   Disc

Log off:

logoff 2

or from Task Manager → Users tab.

Cause 2: Orphaned/Disconnected Session Exists

A previous bot execution may have left a disconnected session.

Check:

query user  or  qwinsta

Look for:   Disc    or Disconnected sessions.

Fix  – Verify Session Limits

Open:

gpedit.msc

Navigate:

Computer Configuration
 └ Administrative Templates
     └ Windows Components
         └ Remote Desktop Services
             └ Remote Desktop Session Host

Check:

Limit number of connections
Restrict Remote Desktop Services users to a single session

Cause 3: Multi-user Bot Runner Configuration Issue

The log indicates:

It appears to be a multi user session deployment

If the device is configured for:

• Multi-user bot runner
• Limited session count

AA cannot create another session.

FIX : Restart Stuck Sessions

If safe to do so:  rwinsta <sessionID>

Example:   rwinsta 18

This resets the session.

Cause 4: Session Reuse Configuration Mismatch

Automation Anywhere attempted:

reuse existing session if available  but

Could not find an existing session that matches session key

Possible reasons:

• Different domain/user combination
• Existing session owned by another account
• Session metadata out of sync

FIX : Verify Automation Anywhere Device Settings

In Automation Anywhere Control Room:

1. Devices
2. Bot Runner Device
3. Session Management

Check:

• Maximum concurrent sessions
• Multi-user session settings
• Session reuse settings

Fix 5 – Restart Bot Agent / Node Manager

Sometimes the session cache becomes stale.

Restart:

Automation Anywhere Bot Agent
Automation Anywhere Node Manager

or reboot the Bot Runner server.

Commands to Run Immediately

On the Bot Runner server:

query user   and   qwinsta

Look for:

• Active sessions
• Disconnected sessions

Multiple sessions for the bot user

​@GOAA  provided solutions based on the log, it may be available after AA moderator review 

​@Lu.Hunnicutt  can you help moderator to review my reply on  ​@GOAA  provided logs ?

​@rbkadiyam ​@GOAA Good now. See ​@rbkadiyam ‘s response above

Hello ​@rbkadiyam 

I response all WorkAround scenaries

Cause 1: Windows RDP Session Limit Reached

No user session is connected

Cause 2: Orphaned/Disconnected Session Exists

No user session is connected in query user and TAsk Manager

The gpos are setting like “Not Defined”

Cause 3: Multi-user Bot Runner Configuration Issue

The setting is Single user RDP, but with multiuser, i have the same issue.

Cause 4: Session Reuse Configuration Mismatch

Single user

Reuse a session, but create a new session if not available.

All setting is configurate to lock the session, never logoff. But i try many configurations here and doesn’t work.

Fix 5 – Restart Bot Agent / Node Manager

I restarted the AA Bot Agent, But i don’t know the Node manager service.

If i did a clean install, deleting everithing y reinstall the agent, the session works fine. But when the session close fails again

Only works with regular session.