Applies to: Player 5.0 for ArcGIS Pro, Player 4.4 for ArcMap
Supported Platforms and Software Environment
Player is an extension to ArcGIS Desktop from Esri, running in either the ArcMap or ArcGIS Pro applications. It has the same system requirements and supports the same matrix of Supported platforms as Esri:
However GIS-PAX only certifies Player for the following operating systems:
Windows 7 Ultimate, Professional, and Enterprise 64 bit
Windows 10 Home, Pro and Enterprise 64 bit
Esri also support ArcGIS Desktop running in various on-premise and cloud environments. Internally GIS-PAX uses VMWare Workstation and VMWare Fusion for development and testing of Player and Player for ArcSDE. Other platforms are expected to work, contact GIS-PAX Support for the latest support on these environments.
GIS-PAX certifies the following software releases of ArcGIS Desktop and ArcGIS Pro:
- ArcGIS Desktop 10.3 up to 10.3.1
- ArcGIS Desktop 10.4 up to 10.4.1
- ArcGIS Desktop 10.5 up to 10.5.1
- ArcGIS Desktop 10.6 up to 10.6.1
- ArcGIS Desktop 10.7
- ArcGIS Pro 2.2 up to ArcGIS Pro 2.3 (also requires either ArcGIS ArcGIS Engine 10.3 or greater; or alternatively ArcGIS Desktop 10.3 or greater)
Player is an extension/addin to ArcGIS Desktop, licensed separately through Esri. ArcGIS Desktop is available in three license levels: Basic, Standard, or Advanced. The complete Player workflow can be carried out using an ArcGIS Desktop Basic license except for:
- Player for ArcSDE – moving the Player database to an ArcSDE enterprise geodatabase and allowing geologists to do multi-user editing requires at least an ArcGIS Desktop Standard license.
- PlayPen – our functionality for working with raster dataset requires the ArcGIS Spatial Analyst extension.
- Player 5.0 for ArcGIS Pro – in addition to an ArcGIS Pro license (minimum Basic) Player requires an appropriate license for either ArcGIS ArcGIS Engine 10.3 or greater; or alternatively ArcGIS Desktop 10.3 of greater (more on this below).
- ArcMap 10.3 to 10.6 and Player 5.0 for ArcGIS Pro requires an additional Microsoft library to open Excel XLSX files. More information is available below on these components. The download is available from the GIS-PAX Helpdesk: 2007 Office System Driver: Data Connectivity Components.
- DocLibrary preview uses the native preview capability in Windows. The following file types require:
- PDF documents - Adobe Reader
- Office documents – Office 2012 or greater
Enterprise geodatabase support
Player supports data in either an Esri file geodatabase or an ArcSDE geodatabase. You require additional licensing from GIS-PAX to access a Player geodatabase in ArcSDE.
As Player runs as an extension to ArcGIS Desktop/Pro it has the same system requirements and supports the same matrix of database platforms and versions. However GIS-PAX only certifies Oracle and SQL Server on Windows Server 2012 R2 Standard and Datacenter 64 bit and Windows Server 2016 Standard and Datacenter 64 bit:
Player 4.4 (Build 6900) and Player 5.0 (Build 6900) has been tested with ArcSDE 10.5 on the following databases:
- Oracle Standard/Standard One/Enterprise editions:
- Oracle 12c R2 (64-bit) 184.108.40.206
- SQL Server editions:
- Microsoft SQL Server 2017 (64-bit)
Player 5.0 for ArcGIS Pro still has a dependency on ArcObjects
Player 4.4 and Player 5.0 run from the same set of dlls for both ArcMap and Pro. This allows GIS-PAX to provide same functionality for geologists in both versions. GIS-PAX have committed to support Player 4.x for ArcMap until at least the end of 2019. Depending on how many of our customers have migrated to ArcGIS Pro, we will assess this decision and possibly extend this date in Q4 2019.
This means Player 5.0 has a dependency on ArcObjects. If ArcGIS Desktop is not installed, the MSI installer and Player software tests if ArcGIS Engine is installed. If a supported version of ArcGIS Engine is available, Player can be installed and will run on ArcGIS Pro.
ArcGIS Engine is a separate component from Esri. There is no user interface, it is a set of libraries that supports the creation of GIS and mapping applications. To your Player users, they will only have ArcGIS Pro installed. ArcMap will not be installed/available. You can get more information below on ARcGIS Engine to understand its capabilities:
We expect to have a dependency on ArcObjects for a number of Player 5.x releases. Migrating the Player code to the native Pro SDK will take 12-24 months beyond the end of 2019.
This dependancy does not prevent your organisation from migrating your GIS users off ArcGIS Desktop and decommissioning extensions to ArcMap. The Player 5.0 for ArcGIS Pro implementation supports this. ArcGIS Engine is not visible to your GIS users, they interact with Player in Pro only.
2007 Office System Driver: Data Connectivity Components
When Microsoft released Office 2007, it included support for the XLSX file format (using the Office Open XML file format). For external applications like Esri ArcGIS Desktop to read an XLSX file, Office 2007 needed to be installed. If Office 2007 wasn't installed, Microsoft provided an alternative set of components, the Office System Driver: Data Connectivity Components These are a set of components for transfer of data between 2007 Microsoft Office System files and non-Microsoft Office applications.
The Office System Driver: Data Connectivity Components are 32-bit binaries. ESRI requires this 32-bit component for ArcObjects (the software components ArcGIS Desktop [ArcMap] or ArcGIS Engine are built with) to read XLSX files. As Player is based on ArcObjects (on both ArcMap and ArcGIS Pro) it has the same requirement. When Player is migrated away from ArcObjects to the ArcGIS Pro SDK, that the dependency is no longer required.
Most importantly, the Office System Driver: Data Connectivity Components are not related to the version of Office365 software installed on a users computer. Office365 does not use these components in any way.
Microsoft have stopped providing the components on their Downloads website. However they are still available from the GIS-PAX Support website:
Office System Driver: Data Connectivity Components
To install the AccessDatabaseEngine.exe do the following:
- Download the file by clicking the Office System Driver: Data Connectivity Components (above) and saving the file to your hard disk.
- In File Explorer, remove the exe from the zip file.
- Double click the AccessDatabaseEngine.exe program file on your hard disk to start the setup program.
- Follow the instructions on the screen to complete the installation.
To remove this Download:
- To remove the download file itself, delete the file AccessDatabaseEngine.exe
On the Start menu, point to Settings and then click Control Panel.
Double-click Add/Remove Programs.
- In the list of currently installed programs, select “Microsoft Office Access database engine 2007” and then click Remove or Add/Remove.
- If a dialog box appears, follow the instructions to remove the program.
Click Yes or OK to confirm that you want to remove the program.