If the domains drop-down list is empty

Troubleshooting instructions if there are no domains populated in the domain drop-down list on the Control Room login page.

This issue can occur when one of the Key Distribution Centers (KDC) servers is not responding, causing a long delay. If Control Room is configured with Active Domain authentication, but after an upgrade there are no domains populated in the domain drop-down list on the Control Room login page, follow these steps to fix the error:

Procedure

  1. Stop the following Control Room services:
    • Control Room Caching
    • Control Room Messaging
    • Control Room Service
    • Control Room Reverse Proxy
  2. Make a copy of the um.properties file that is located in the folder where Control Room is installed on your environment.
    The default file path is C:\Program Files\Automation Anywhere\Enterprise\config\um.properties.
  3. Open the copy file as an administrator.
  4. Obtain a list of KDC for all of your domains/forests.
    A KDC is the domain controller which serves the Kerberos tickets from users/computers.
    1. Run the following example command in the Command Prompt. Replace domain.com with your Control Room domain.
      nslookup -type=srv _kerberos._tcp.DOMAIN.COM
    2. Find the KDCs for each domain in the output lines that start with svr hostname = .
    3. Add the following example entry at the end of the file, replacing domain1.com and domain2.com with your domain names, and host1, host2, and host3 with the KDCs for each domain.
      um.ldap.kdcs='domain1.com:host1.domain1.com:host2.domain1.com:host3.domain1.com,domain2.com:host4.domain2.com:host5.domain2.com'
      Note: The domain must be the first token, followed by one or more KDCs separated by colons and each domain separated by commas.
  5. Save and close the file.
  6. Start the following Control Room services:
    • Control Room Caching
    • Control Room Messaging
    • Control Room Service
    • Control Room Reverse Proxy

Next steps

If the Control Room is running in a cluster environment, repeat these steps for each node.