No access to UT feature classes despite UT installation

Problem:

Accessing UT feature classes with an external program, such as ArcReader, FME, Python, MxdPerfStat (here the UT layers are not displayed), etc., does not succeed, despite the fact that

• UT or at least the UT Components are installed.

However, access via ArcCatalog, ArcMap or ArcGIS Server works.

Cause:

This behavior occurs if on the computer on which you run the program,

• a higher ArcGIS version than 10.6.1 is installed and
• the assembly binding via *.exe.config is not set.

The assemblies of UT are compiled against ArcGIS version 10.6.1. As a consequence ArcGIS assemblies in version 10.6.1 are searched but not found. The programs must be notified that more recent versions of the ArcGIS assemblies can be used. This is done via the assembly binding in the *.exe.config to the respective programs.

When installing ArcGIS this is already done for the ArcGIS programs. When installing UT for ArcGIS the *.exe.config for

• ArcCatalog,
• ArcMap and
• ArcGIS Server

are extended with the UT assemblies and corresponding *.exe.config are created for the UT programs. For other programs, the assembly binding is still missing in the *.exe.config and must be done by you.

Solution:

For external programs, the *.exe.config files with the assembly binding must also be created. If such a file does not exist yet, you can copy the ArcMap.exe.config into the respective directory to the *.exe and rename it according to the program name. If such a file already exists, the configuration from the ArcMap.exe.config has to be copied into the existing *.exe.config.

Known application configurations are for example:

• FME Desktop
  • FME.exe.config
  • FMEDataInspector.exe.config
  • FMEWorkbench.exe.config
  • FMEWorker.exe.config
• FME Server
  • FMEConnection.exe.config
  • FMEEngine.exe.config
• Python
  • Python.exe.config
  • PythonW.exe.config
• MXDPerfStat
  • MXDPerfStat10x.exe.config