Skip to main content

I THINK I am on the Developer Path Dashboard. I am trying to create my first task bot from the RPA Demo video. (Again, I think this is part of the Developer Path Course although it doesnt identify anywhere it being Week 1 or 2, or so on.) However, when I am trying to run the test bot, I keep getting an error saying I am not logged in. I have tried everything I know of and am unable to get the test bot to run. I dont know where to go from here.

Are you getting this message?
 

If so, go to your name (or initials) on the far left side menu and click My Settings. Inside that screen, select Devices. In the row titled Credentials, put in your computer’s local name and your local username.

You can get this information by bringing up a command prompt (or Terminal or PowerShell) and entering “whoami” (without the quotes) and pressing ENTER. It will respond with something like this:

mydomain\myusername

Put that value into the username field in the Credentials. No password is needed. Then click Save changes.


@Aaron.Gleason ,

This was the exact message I was getting and your solution was spot on.  WHOOP!  I just completed the first test bot successfully!  I may be behind in the schedule, but I am now on my way.  Thanks!


Ok, so that solution did work.  HOWEVER, when I am trying to configure the Browser:Open task, I am not able to select “Google Chrome” from the within the exercise.  When I do, I get the following error: 

If I select “Default Browser” instead, the bot will run without error.  HOWEVER, when I run it that way, I am not able to create the nest step in the exercise, the Capture step.  When I try to add the Capture step after running the bot to “Default Browser” instead of Chrome, I dont see the window or tab in the list.  Maybe I need office hours to walk through this...

 


@Aaron.Gleason , I forgot to tag you on the other reply above with the screenshot.  Thanks


No worries, ​@christophergarzaLYB. That second issue is a strange one… one I haven’t seen before. Can you launch Microsoft Edge successfully by specifying that browser? If so, when it launches, are the tabs visible?

 


@Aaron.Gleason Ok, so selecting Edge worked.  When I ran the bot, it did in fact open Edge in a new window.  Then once I went to the Capture step and tried to refresh the available browsers to select Edge/the “Welcome to AA Test Page”, I get the following error:  :( 

THANK YOU for working with me on this!


@Aaron.Gleason or ​@Oli.Morris , I am completely stuck at this point.  I follow the steps in building the automation exactly (although in Edge instead of Chrome) and everything works just fine until I try to refresh the list of Browser options in the Capture step of the video (timestamp 7:03).  The open Edge window (that opened, and I never closed, when I tested the first automation) is still open, but is not listed in the options, as the video states it will not be.  However, when I refresh the list, as instructed in the video, I get this error: 

I’m at a loss if where to go from here.  I cant get this step to work in either Chrome or Edge.  I’m stuck.  :( 

 


Very odd. Between Chrome not launching and Edge being weird, I would say there is some security software that is hampering things. Just a guess, but if you're using a company-provided computer, I might as your IT department. 

The only time I see that error is if there are no Chrome or Edge windows open. (Yes, you can use Firefox technically unsupported] for the control room and Chrome/Edge for your automations.) I might try turning the Automation Anywhere extension off in Edge and back on to reload it. 


Yes, thank you, ​@Aaron.Gleason 

I am thinking, as you are, that there is some security prompt or issue that is not allowing the Control Room to see which Windows I have open which is causing the error.  I can match the exercise exactly until the Capture step because I cannot get the window to pop in the drop down list.  I tried the “open the lock” exercise and had the same exact experience.  I will give the turn off and reload extension a try.  I am also conversating with some LYB colleagues via Teams to see if they can assist the troubleshooting efforts.  Thanks again for all of your help on this.  


Reply