The following are known issues at the time of release, as well as system and software limitations.

CSRF Detection Issues

Changes were made in 2024 R1 which require more explicit remote host specification in some configurations. For example, if an ADR server is accessed via a proxy web server, the hostname and protocol of the proxy server must be made available to Ansys Dynamic Reporting. These kinds of problems show up in various situations, but two are fairly common. First, if you try to log into the ADR server, you can be presented with a page reporting a CSRF problem (403 error). Second, it may not be possible to create/update any content in the server (for example, upload new data, create a new template, and so on).

This can be fixed by explicitly telling ADR what hostnames to trust for CSRF purposes. For example, if the ADR server is running behind a proxy server which is used for handling SSL. In cases like this, set the CEI_NEXUS_TRUSTED_ORIGINS environment variable to the domain name(s) of the trusted proxy. For example:

export CEI_NEXUS_TRUSTED_ORIGINS="https://*.example.com"
adr_launcher start --db_directory /my/database/directory

The CEI_NEXUS_TRUSTED_ORIGINS environment variable is a list of trusted origins for unsafe requests (like. POST). It can be in one or more of the following forms:

More than one trusted server can be included by separating them by commas in the environment variable.

Internet Explorer Support

The Ansys Dynamic Reporting web interface does not support Internet Explorer.

EnSight and Template Editor

Logging in and out of the Ansys Dynamic Reporting web interface when embedded inside the Ansys Dynamic Reporting Template Editor or EnSight is not supported. Disconnect from the server using the File menu and reconnect with the new credentials to switch users.

UNC Paths

Launching an ADR server from a UNC location on a Windows system is not supported.

Network Delay Ansys Dynamic Reporting Session Limitations

Integrated operation of Ansys Dynamic Reporting with EnSight and EnVision is reliant upon high performance network connections between the components, display environments (. frames in a browser) and distribution installation location (for example, network file system installs). There are a variety of implied timeouts within and between these components which can disrupt successful launching of these applications within specific environments.

Some Ansys Dynamic Reporting configurations involving slower virtual machines and the Firefox web browser have been observed running into problems displaying remote, embedded EnVision sessions. In such cases, switching to browsers with longer default web acknowledgment timeouts (like Chrome) or using higher performance virtual machines can help. Problems have also been observed when running Ansys Dynamic Reporting from software installations on remote (NFS) file systems with slower input/output response or limited remote file locking mechanisms. In these cases, moving the Ansys Dynamic Reporting database and/or the software installation to local disk storage can avoid excessive operational timeouts.

Inability to Create New/Start Databases On Linux

Ansys Dynamic Reporting relies on the platform-specific time zone specification being correct. On some Linux systems, it can be configured in an ambiguous fashion (different environment variables pointing to differently named time zones). On these systems, the Ansys Dynamic Reporting APIs for creating a new database or launching a server may fail. The following test can be used to check to see if the system is configured incorrectly (use the v251/CEI/bin/cpython Python executable).

import tzlocal
print(tzlocal.get_localzone_name())

If this code raises an exception, the system has not been configured correctly. Setting the TZ environment variable to a valid time zone specification like US/Eastern will work around the issue.