There might be a temporary outage. Please try after some time.

​@e.tamilselvan Are you able to login now?

​@Lu.Hunnicutt Yes, I am now able to log in.

​@e.tamilselvan 

Possible Causes

1. Server Overload or Maintenance:
   • The Control Room server might be undergoing maintenance, experiencing high traffic, or facing resource constraints.
2. Network Issues:
   • Connectivity problems between your device and the Control Room server could trigger this error.
3. Service Disruption:
   • One or more Automation Anywhere services (e.g., Control Room, database) might be down or restarting.
4. Configuration Issue:
   • If it’s an on-premise deployment, a misconfiguration in the server setup (e.g., load balancer, reverse proxy) could be the culprit.

Steps to Resolve the "503 Service Temporarily Unavailable" Error

1. Wait and Retry:
   • Since a 503 error is temporary, wait a few minutes (5-10) and try logging in again. This is often the simplest fix if the server is undergoing a brief overload or restart.
2. Check Your Internet Connection:
   • Ensure your network is stable. Test by opening other websites or pinging the Control Room URL (e.g., ping yourcontrolroomurl.com).
   • If you’re on a VPN, disconnect and reconnect, or switch networks to rule out connectivity issues.
3. Clear Browser Cache:
   • A corrupted cache might interfere with the login process:
     • Open your browser in incognito mode and try logging in.
     • Alternatively, clear the cache and cookies (e.g., in Chrome: Settings > Privacy and Security > Clear Browsing Data).
4. Verify Control Room Status:
   • If you’re using Automation Anywhere’s cloud-hosted solution, check the Automation Anywhere status page (if available) or contact your administrator to confirm if there’s a known outage.
   • For on-premise setups, ask your IT team to verify the server status.
5. Use a Different Device or Browser:
   • Test logging in from another device or browser to isolate whether the issue is device-specific or browser-related.

For Administrators (On-Premise Setup)

If you have admin access to the Control Room, try these steps:

1. Check Server Status:
   • Log in to the server hosting the Control Room.
   • Open services.msc and ensure all Automation Anywhere services (e.g., "Automation Anywhere Control Room," "Automation Anywhere Bot Agent Service") are running.
   • Restart any stopped services:
     • Right-click the service > Restart.
2. Review Server Resources:
   • Check CPU, memory, and disk usage on the server. A 503 error can occur if resources are maxed out:
     • Open Task Manager or Resource Monitor.
     • If usage is high, scale up resources (e.g., add RAM, CPU) or stop unnecessary processes.
3. Inspect Load Balancer (if applicable):
   • If your Control Room uses a load balancer, ensure it’s routing traffic correctly:
     • Check the load balancer’s health status for all nodes.
     • Restart the load balancer service if needed.
4. Check Database Connectivity:
   • The Control Room relies on a database (e.g., Microsoft SQL Server, PostgreSQL). A 503 error can occur if the database is unreachable:
     • Verify the database service is running on its server.
     • Test connectivity from the Control Room server to the database server (e.g., ping <database_server_ip> or use SQL Management Studio).
5. Review Logs:
   • Check the Control Room logs for detailed errors:
     • Location: Typically in C:\Program Files\Automation Anywhere\Control Room\logs (adjust based on your installation path).
     • Look for entries around the time of the 503 error to identify the root cause (e.g., database timeout, service failure).
   • Also, check the Audit Log in the Control Room UI (Administration > Audit Log) if you can access it.
6. Restart the Control Room:
   • If all services are running but the issue persists, perform a full restart:
     • Stop all Automation Anywhere services.
     • Restart the server.
     • Start the services again in the correct order (database first, then Control Room).

If the Issue Persists

• Contact Support:

  

   

• If you’re on a cloud-hosted instance or unable to resolve it on-premise, raise a ticket with Automation Anywhere support via the Automation anywhere Customer portal(Customer Portal) and
• Provide below details:
  • The exact error message ("503 Service Temporarily Unavailable").
  • The time of occurrence (in your timezone).
  • Server logs (if accessible).