JR64771: SCHEDULES, RUNTIMES AND PROCESSES DOES NOT WORK IN IBM RPA WITH CLIENT AND SERVER ON DIFFERENT MACHINES

APAR status

• Closed as program error.

Error description

• Schedules, runtimes, and processes do not work in IBM RPA with
  client and server on different machines
  
  When opening the agent logs, users may see:
  Fail to start computer queue (COMPUTER_NAME):
  System.AggregateException: One or more errors occurred. --->
  System.AggregateException: One or more errors occurred. --->
  System.Messaging.MessageQueueException: Access to Message
  Queuing system is denied.
  Or
  
  Fail to start computer queue (COMPUTER_NAME):
  System.AggregateException: One or more errors occurred. --->
  System.AggregateException: One or more errors occurred. --->
  System.Messaging.MessageQueueException: Access to Message
  Queuing system is denied.
  
  This happens on the communication provided between client and
  server when creating the computer queues within MSMQ, leading
  every operation which involves queues (such as schedules,
  processes, and runtimes) to not being executed.
  

Local fix

• In some cases, reinstalling the MSMQ and creating a new computer
  can help:
  1- Stop the IBM Robotic Process Automation Agent service
  2- Uninstall the MSMQ on Windows (Remove Windows Features)
  3- Create a new computer for the tenant with a different name
  4- Download and Install the newly created computer certificate
  5- Reinstall MSMQ
  6- Start the service: IBM Robotic Process Automation Agent
  service
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * No further information                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to 21.0.2 IF003 or higher                             *
  ****************************************************************
  

Problem conclusion

• First fixed in 21.0.2 IF003
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RPA

• Fixed component ID

  5737N5100

Applicable component levels