cancel
Showing results for 
Search instead for 
Did you mean: 

Logint Agent Issues

HadyEl_Masri
Level 2
Hello,

I am currently testing the Login Process from the Login Agent in Blue Prism.

I have set up my scheduler to run the Login Process once every 5 minutes to test if it would actually login to my user or not. I defined the necessary credentials required for the login, followed the security protocols (i.e removed the ctrl + alt + delete before the username and password), declared the startup parameters inside the scheduler, etc. 

Unfortunately, I haven't managed to make the process work accordingly, and login into my pc. I did some digging and this seems to be the issue that I get when the scheduler runs the process: "ERROR: Exception : 0x80131505: The operation has timed out." 

I also obtained this from the logging file used by the Login Agent:

TSS(Remote) 5: 09:12:23:0686 DEBUG BluePrismProvider.cpp(392): Setting provider usage scenario: Logon

TSS(Remote) 5: 09:12:23:0687 DEBUG BluePrismCredential.cpp(44): BluePrismCredential instance created

TSS(Remote) 5: 09:12:23:0687 DEBUG BluePrismProvider.cpp(85): Listener Thread - starting

TSS(Remote) 5: 09:12:23:0689 TRACE helpers.cpp(83): FieldDescriptorCopy()

TSS(Remote) 5: 09:12:23:0689 DEBUG BluePrismProvider.cpp(124): Listener Thread - finishing

TSS(Remote) 5: 09:12:23:0689 TRACE helpers.cpp(83): FieldDescriptorCopy()

TSS(Remote) 5: 09:12:23:0689 TRACE helpers.cpp(83): FieldDescriptorCopy()

TSS(Remote) 5: 09:12:23:0690 TRACE helpers.cpp(83): FieldDescriptorCopy()

TSS(Remote) 5: 09:12:23:0690 TRACE helpers.cpp(83): FieldDescriptorCopy()

TSS(Remote) 5: 09:12:23:0690 DEBUG BluePrismProvider.cpp(410): BluePrismProvider instance created

TSS(Remote) 5: 09:12:23:0693 DEBUG BluePrismProvider.cpp(458): Provider callback enabled

TSS(Remote) 5: 09:12:23:0695 DEBUG BluePrismProvider.cpp(520): Getting Credential Count: 0

TSS(Remote) 5: 09:12:30:0720 DEBUG BluePrismProvider.cpp(472): Provider callback disabled

TSS(Remote) 5: 09:12:30:0721 DEBUG BluePrismProvider.cpp(67): Listener Thread Completed

TSS(Remote) 5: 09:12:30:0721 DEBUG BluePrismCredential.cpp(58): BluePrismCredential instance destroyed

Any help on the subject would be appreciated, thank you.



------------------------------
Hady El Masri
------------------------------
5 REPLIES 5

MaxElopre
Level 5
Please check out the thread on this issue:
https://community.blueprism.com/communities/community-home/digestviewer/viewthread?GroupId=97&MessageKey=9131761c-aeb2-4875-9300-30ac6da81179&CommunityKey=3743dbaa-6766-4a4d-b7ed-9a98b6b1dd01&tab=dige...

------------------------------
Max Elopre
Technical Consultant
Chicago IL
------------------------------

peterlacken
Level 7
Hi,

You must restart the pc after an installation of login agent. check that the service is installed and running on the target pc - Blue Prism Login Agent. Check the event logs on the pc for time that you tried to login for extra error info.

Peter

------------------------------
PeterLacken
Ren Røros Intelligent Automation
Peter.Lacken@rria.no
http://www.rria.no
------------------------------

Hello,

Thank you for your prompt reply.

I have checked the post that you have linked, and followed the steps provided by Luis Lopez. Unfortunately, this has not solved the issue and I am currently out of ideas on what we can try.

I have also made sure that I don't get a message before the username/password area as suggested by Max Elopre.

------------------------------
Hady El Masri
------------------------------

Have you installed the correct Version of Login Agent? If you are on a later Version Of BP then Login Agent comes with the application under the «Installers» directory. Don't use the version on the portal. Can you post a screen shot of the Control Room and the Login process Log error Message?

------------------------------
PeterLacken
Ren Røros Intelligent Automation
Peter.Lacken@rria.no
http://www.rria.no
------------------------------

jinilseb
Level 3

Hi,
Sorry for the late bump.
I am also getting the same timeout error and the same details in the login agent logs. 
@HadyEl_Masri  Did you manage to find out and resolve the issue ?