Question

3
Replies
227
Views
SasidharB9516 Member since 2017 31 posts
Morgan Stanley
Posted: 1 year ago
Last activity: 1 year 11 months ago
Closed

ROBOT Shcheduler - Unable to login to VM via BOT scheduler service

Coming across below error

2018-10-17 09:57:55 AM - INFO – [1] - *** Initializing ***
2018-10-17 09:57:55 AM - DEBUG – [1] - Interactive: True
2018-10-17 09:57:55 AM - DEBUG – [1] - Interactive domain: xxxx
2018-10-17 09:57:55 AM - DEBUG – [1] - Interactive user: SYSTEM
2018-10-17 09:57:55 AM - DEBUG – [1] - Mode: terminate Runtime
2018-10-17 09:57:55 AM - DEBUG – [1] - User domain: xxxx
2018-10-17 09:57:55 AM - DEBUG – [1] - User name: yyyyyy
2018-10-17 09:57:55 AM - DEBUG – [1] - Password: -provided-
2018-10-17 09:57:55 AM - DEBUG – [1] - Lock status: locked
2018-10-17 09:57:55 AM - DEBUG – [1] - Logon disclaimer processing: enabled
2018-10-17 09:57:55 AM - DEBUG – [1] - Logon disclaimer wait: 0
2018-10-17 09:57:55 AM - INFO – [1] - Initialized
2018-10-17 09:57:55 AM - DEBUG – [1] - Server OS version 6.2.9200.0 detected
2018-10-17 09:57:55 AM - DEBUG – [1] - Windows Server 2012 logon resolver
2018-10-17 09:57:55 AM - DEBUG – [1] - Session - active session Id # 1
2018-10-17 09:57:55 AM - DEBUG – [1] - Lock screen process Id is 752
2018-10-17 09:57:55 AM - DEBUG – [1] - Session - collected session: Id # 2, domain: xxxx, user: yyyyyyy, state: WTSActive, active: True
2018-10-17 09:57:55 AM - DEBUG – [1] - Session - collected 1 session(s)
2018-10-17 09:57:55 AM - DEBUG – [1] - Session - active session user is xxxx\yyyyyyy
2018-10-17 09:57:55 AM - DEBUG – [1] - Process last logged in user xxxx\yyyyyyy
2018-10-17 09:57:55 AM - DEBUG – [1] - Collect all accessibility controls for LogonUI
2018-10-17 09:57:55 AM - DEBUG – [1] - Accessibility - Role Id: 16, role name: pane , name: Sign-in frame , value: .
2018-10-17 09:57:55 AM - DEBUG – [1] - Accessibility - Role Id: 41, role name: text , name: Access and use of zzzzzzzzzzzzzzzz (the “Firm”) systems is only permitted for Firm
business and limited personal use. “Firm Systems” include approved verbal and
electronic messaging systems and other communication facilities, (such as
telephones, facsimile, SMS, instant message, email, Bloomberg and any other
electronic or recordable communications), and technology owned by or made
accessible by the Firm or any other persons acting on its behalf, (such as systems
that facilitate communications, information processing, transmission, storage and
access, as well as remote access). Firm business must only be conducted using Firm
Systems and in accordance with Firm policies. You should not access Firm Systems
which are not related to your role or job responsibilities and for which you would not
reasonably need to have access. Subject to applicable laws, the Firm monitors your
access to and use of Firm Systems and any data moving through and/or residing on
Firm Systems and retains electronic communications, regardless of whether they have
been deleted from your computer or wireless device. For further information refer to the
Global Monitoring Notice. You should not use Firms Systems for personal use if you do
not wish your personal use and communication to be monitored. Failure to comply with
Firm policies may result in disciplinary action, up to and including termination of
employment or engagement and any other applicable legal (civil or criminal) or
regulatory action. By clicking on “ok” you acknowledge that you have read and
understand this notification, (including the Global Monitoring Notice)., value: .
2018-10-17 09:57:55 AM - DEBUG – [1] - Accessibility - Role Id: 41, role name: text , name: Firm Systems Login Notification, value: .
2018-10-17 09:57:55 AM - DEBUG – [1] - Accessibility - Role Id: 43, role name: push button , name: OK , value: .
2018-10-17 09:57:55 AM - DEBUG – [1] - Collected 4 accessibility controls for LogonUI
2018-10-17 09:57:55 AM - DEBUG – [1] - User name control is not found
2018-10-17 09:57:55 AM - INFO – [1] - xxxx\yyyyyyy screen unlock is unsuccessful

Robotic Process Automation
Moderation Team has archived post
Share this page LinkedIn