Consolidated exercise process on runtime resource with login agent

[AustinPoeh]

I am new to BP and not an IT guy. I'm a data analyst. Please be understanding with my lack of IT knowledge. I am also the sole person using BP where I work. 

BP version 6.9.0

Our ultimate goal is to create and schedule processes to run on BPRUNTIME1 overnight with nobody online to start it. 

I have completed the Consolidated Exercise and another process. Both processes complete on my laptop, but when I use the login agent to run them on the virtual machine (BPRUNTIME1) set up as a runtime resource, they both fail on the first stage.

I am able to run the Stopping Time Exercise on BPRUNTIME1 using the login agent. It appears when BP needs to do something outside of itself, it terminates on the first stage. 

I have checked the file paths. I have logged into BPRUNTIME1 as the windows user that the login agent uses and both processes will complete. 

I don't know if BPRUNTIME1 isn't set up correctly, the login agent isn't set up correctly, or if the processes aren't set up correctly. 

Any help is appreciated!

[lookman]

Hi Austin.

I'm glad you were able to find the doc at least. I don't know why you wouldn't be able to access Login Agent training. 

I suggest you create a new post and ask that question specifically. There are folks monitoring the messages (like me) that know about access issues in the LMS and hopefully one of them will pick it up quickly and get an answer for you.

jack

[AustinPoeh]

Jack: 

Will do.

Astrid: I'm getting the document over to IT and hopefully we'll get this figured out (if not I'll be back).

Thank you both for your help!

[AustinPoeh]

Astrid:

I tried searching the community for the below error, but didn't have any luck. I also looked at the login agent object and it appears to come from the Authenticate To Windows page. I noticed that page isn't published. I believe we have the listener set up correctly, but when I run the login agent I get this error: 

[astrid.stollberger]

Dear Austin,

sometimes the issue isn't within Blue Prism and the exception happens somewhere else it's just Blue Prism which catches it and passes the error message on to the user.
So although the Blue Prism community should probably be the first place to search, it shouldn't be the only one 🙂
A quick google search for this semaphore timeout error points to some sort of network issue:
https://www.stellarinfo.com/blog/solved-error-semaphore-timeout-period-has-expired/

Are there maybe any firewalls blocking the access of the login agent to your VM?

Cheers
Astrid