topic Have you resolved this issue? in Product Forum

Cannot login to resource PC using login object

sanmeetgurudatt — Tue, 01 Aug 2017 21:39:00 GMT

Hi, When the machine is restarted I can the see the resource machine being connected in the control room using login agent, but when I try to login using login object it won't throw any error but still it fails to Login(Logout and lock works), I made sure the credentials in the credential manager is correct, has anyone faced the same issue? please let me know if you have a solution. Thanks

Sounds like you have got

John__Carter — Wed, 02 Aug 2017 14:14:00 GMT

Sounds like you have got Login Agent installed correctly if the logged out Resource PC is online in Control Room. The Logout and Lock processes are run on the logged in Resource PC, whereas the Login process is run on the logged out Resource PC. Have you checked that the PC is set up correctly - is CTRL ALT DEL disabled etc, as specified in the Login Agent documentation?

I will configure as per the

sanmeetgurudatt — Wed, 02 Aug 2017 21:27:00 GMT

I will configure as per the document, but I noticed one more thing the business objects such as Is Logged In results false and get user list results zero collection but only object works is Lock, any suggestion to fix this first? Thanks

I will configure as per the

sanmeetgurudatt — Wed, 02 Aug 2017 21:27:00 GMT

Have you upgraded BP

TomaszAdamski — Thu, 03 Aug 2017 12:50:00 GMT

Have you upgraded BP installation since you installed the Login Agent? I noticed some issues after upgrading BP so I had to (re)import VBOs which came with the newer version. It solved problems with two VBOs so I decided to re-import all of them afterwards... just in case 😉

No I haven't upgraded BP, It

sanmeetgurudatt — Fri, 04 Aug 2017 13:55:00 GMT

No I haven't upgraded BP, It doesn't work in few machines, for example: Is Logged In results in False even if the machine is logged in, but it works in Few machines.

Have you resolved this issue?

TomMaloney1 — Wed, 31 Jan 2018 21:34:00 GMT

Have you resolved this issue?