Excel data binding error - The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

When we try to execute a test list on a remote Execution/Scheduling (all in one) Server, we get an exception:

[06/19 12:02:55,ArtOfTest.Runner.exe(436:1),Error] ExcelDataSource.GetDataUnfiltered() : EXCEPTION! (see below)
     Situation: Error reading from Excel database.
     Outer Exception Type: System.InvalidOperationException
     Message: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
     HRESULT: 0x80131509 (Official ID (if app.) = COR_E_INVALIDOPERATION, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5385)
     Call Stack:
          at System.Data.OleDb.OleDbServicesWrapper.GetDataSource(OleDbConnectionString constr, DataSourceWrapper& datasrcWrapper)
          at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
          at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)

This test uses data binding (Excel) to perform the test. A similar error message appeared in another forum thread. Telerik's last response provided a link to their documentation that states that Microsoft Access Database Engine 2010 needs to be installed. Our team installed this on the Execution/Scheduling Server, but the same exception is occurring. The server was restarted and the we tried re-installed Microsoft Access Database Engine 2010 to no avail.

The thread referenced above also referred to 2007 Office System Driver: Data Connectivity Components, which is a broken link, and I'm guessing that Microsoft Access Database Engine 2010 is the now recommended version since it is in your documentation.

To note, when a test list does not use an Excel data binding, the test runs properly.

________________________________________________________________________________________________

Environment Description:

• Server 1: Scheduling and Execution (Test Studio Runtime)
• Server 2: Test Studio where testers create tests. They run these tests remotely on Server 1.