Proctor

• Proctor log is present under the path <<Proctor installation path>>\Proctor\logs\Proctor.log.
• After installing Proctor, if the Proctor machine fails to appear in Control Tower under the Machines View, check the logs available at the path mentioned above. If the log contains an error related to the certificate, it could be that the certificate is not installed or correct certificate is not installed, or multiple copies of the certificate are present in the manage user certificate.
• In the Update Agent screen, if you are updating the username, release all the robots associated with the agent before updating the agent. In case only the password or domain is being updated, this step is not required.
• If Add/Update Agent fails, perform the following steps:
  • Check if the user details entered in the Add/Update Agent screen are correct and that the user has remote login access on the machine where Proctor is running. In this case, the Connection failed error appears in the log file.
  • Check if the number of allowed user sessions on the machine where Proctor is running has exceeded.
  • By default, the time required to log in to the Proctor machine is set to 40000 milliseconds in the configuration file. If the actual time required to login is more, make the changes accordingly in the configuration file available at: <<Proctor Installation Path>>\Proctor\EV.AE.Proctor.exe.config.
    
    
    
    Below error usually appears in above case:
     

    "srcmodule":"EV.AE.RemoteDesktop.RemoteConnection","method":"ConnectUser","message":"User 'XXX' connected successfully" "srcmodule":"EV.AE.Proctor.Command.CommandHelper","method":"ConnectUser","message":"User 'XXX' session id is '-1'" Or "srcmodule":"EV.AE.RemoteDesktop.RemoteConnection","method":"ConnectUser","message":"User 'xxx' connected successfully" "srcmodule":"EV.AE.Proctor.Command.CommandHelper","method":"ConnectUser","message":"User 'xxx' session id is '5'" "srcmodule":"EV.AE.RemoteDesktop.RemoteConnection","method":"ExecuteCommand","message":"Executing command Robocopy /S /E D:\\XXX\\Robot\\RobotAgent D:\\XXX\\Robot\\Robot\\Proctor\\Agents\\a8479d28-1c4b-4d34-b15f-7973d7e3a7c6 /XF "srcmodule":"EV.AE.Proctor.Command.CommandHelper","method":"CreateAgent","errormessage":"Error occurred while creating agent"

  • Check if the user is getting any security prompt when connected to the Proctor machine. If yes, a corresponding configuration is available in the configuration file available at: <<Proctor Installation Path>>\Proctor\EV.AE.Proctor.exe.config. The default value is set to false. Change it to true.
    
    
    
  • Configure the number of security prompts that a user gets when logged in to the machine. Edit the below configuration. Default value is set to 1.
    
    
  • By default, the time required to successfully dismiss/close a security prompt is set to 5000 milliseconds. If the actual time required is more than this, edit the below configuration.
    
    
  • Increase the time required to execute commands on the Proctor machine. Default value is 15000 milliseconds.
    
    
  • In case Proctor is not receiving commands, go to ev.ae.se.q.command.proctor.machine queue. If the number of requests and unacknowledged state is more, stop the proctor and purge this queue. Once all requests are purged, start the Proctor.
• If Stop Agent fails, follow the below steps:
  • Sometimes, user is in a disconnected state, and the stop command tries to create the session again and execute the command. In such cases, send the command again or stop the agent manually.
• If Messaging(Rabbit MQ) credentials are changed, follow the below steps to update the RabbitMQ credentials in Proctor:
  • Ensure that Rabbit MQ credentials are updated properly using ae UPDATEPASSWORD RabbitMQ command and it is working fine.
  • On the app server, open the command prompt as administrator.
  • Go to path <<AssistEdge build_path>>\scripts.
  • Run ae proctor-config command. This command generates proctor config file, EV.AE.Messenger with new RabbitMQ details at: <<build_path>>\client-tools\AutomationRuntime\Robot\RobotAgent.
  • Copy the EV.AE.Messenger file from the above location and paste it on the Proctor machine in the Robot\RobotAgent folder.
  • Stop Proctor and run ae proctor-config command on the Proctor machine.
  • Start Proctor once the above steps are completed.