AAE CR runs on the Standard and Datacentre Editions of Microsoft Windows Server 2012 (R2) and Server 2016.

Processor – 8-Core Intel Xeon Processor

RAM – 16 GB

Disk Space – 500 GB

AAE CR can run on Microsoft SQL Server 2012, 2014 (SP1), 2016 & 2017. Microsoft .NET 4.6 framework is also needed.

AAE Client will run on the following operating systems:

• Microsoft Windows Server 2016 – Datacenter or Standard Editions
• Microsoft Windows 8 or 8.1 Pro or Enterprise Edition
• Microsoft Windows Professional Edition
• Microsoft Windows Server 2012 R2 – Standard Edition
• Microsoft Windows Server 2012 – Standard Edition
• Microsoft Windows Server 2008 R2 – Standard Edition
• Microsoft Windows 10* – Pro or Enterprise Editions

*AA does not support Automation using Flex technology, nor does it support triggers for Windows Store or Metro UI apps.

Processor – Minimum 3.5 GHz+ with 4 cores

RAM – 8 GB

Disk Space – 300 MB for installation

Note:

• An average Automation Anywhere script is approximately 100-150 KB in size. Additional free disk space is required to develop automation projects, as Automation Anywhere creates temporary files like screenshots, server logs, audit files etc. during script execution.
• The actual free space required increases with project size. We recommended at least 40-50 GB of free disk space to implement long term projects.
• You might have to upgrade to a higher configuration post installation depending upon product usage. For instance, in MetaBot Designer - log files, Logic creation, etc. might require more disk space later.

Internet Explorer: v10 and v11

Google Chrome: v49 and higher

Microsoft Edge: Only if on a Windows 10 OS.

*Automation through Chrome and Edge is not supported in Metabot

Here are a list of steps to help resolve the issue:

• Check that the SQL server/instance is accessible from Control Room server over a specified port, you can check telnet command to validate connectivity from CR to SQL server over the specified port.
• Make sure you are entering correct SQL server, Port and User details.
• Ensure Database authentication credentials (SQL or Windows) have SysAdmin rights to the Database server/instance.
• If using custom port (besides 1433) use DB connection to provide port with server name. e.g. “SQLserver,<port>”.
• You can try using SSMS or other such tools to validate SQL connection and user access to the provided SQL server and database.

Select this link to download a matrix for creating databases, tables and services.