Installation and upgrade known issues

Several known issues exist with installing or upgrading to Analytics Exchange 15.1.1. If any of the issues apply to your organization, follow the instructions below to ensure a successful installation or upgrade.

Connecting to PostgreSQL database

If your existing Analytics Exchange installation uses a PostgreSQL database, you may encounter a problem when upgrading to AX Server 15.1.1. Very occasionally, the AX Server installer times out when trying to connect to the existing PostgreSQL database.

If the installer hangs after clicking Next in the Configure your Analytics Exchange PostgreSQL database server screen, cancel and then restart the installation. This workaround usually solves the problem.

Single sign-on (SSO)

During the upgrade to AX Server 15.1.1, the aclCas.properties file becomes corrupted and single sign-on stops working in AX 15.1.1. The file stores settings for Analytics Exchange authentication.

To avoid this issue, make a copy of aclCas.properties before you begin the upgrade and use it to overwrite the corrupted file.

1. On the server where AX Server is installed, copy the aclCas.properties file and save it outside the ..\ACL\App directory.

   The default location of the file is:

   C:\ACL\App\Tomcat\conf\aclCas.properties

2. Perform the upgrade of AX Server.

3. Use the saved version of aclCas.properties to overwrite the corrupted version of the file.

4. In Windows Services, restart ACL Analytics Exchange Service.

   Single sign-on should now work normally with Analytics Exchange 15.1.1.

AX Engine Node installation or upgrade

AX Engine Node may not work correctly after installation or upgrade. Follow the steps below to ensure a successful installation, or to troubleshoot an upgrade.

Fresh installation of AX Engine Node

1. Install AX Engine Node in the usual manner.

2. Before adding the engine node in the AX Server Configuration web application, make sure AX Engine Node is running on the server where it is installed.

   In Windows Services, make sure ACL Analytics Exchange Service has a status of Running. If necessary, start the service.

3. In the AX Server Configuration web application, add the engine node and click Update Engine Node Settings.

Upgrade of AX Engine Node

If AX Engine Node stops working after you upgrade and returns an error when running an analytic script, perform the following troubleshooting procedure:

1. In the AX Server Configuration web application, remove the engine node.

2. Make sure AX Engine Node is running on the server where it is installed.

   In Windows Services, make sure ACL Analytics Exchange Service has a status of Running. If necessary, start the service.

3. In the AX Server Configuration web application, re-add the engine node and click Update Engine Node Settings.

AX Engine Node excluded items reinstalled

The Python engine and the optional data connectors are installed when you upgrade an AX Engine Node to version 15.1.1 from version 14.x. The items are installed even if you previously chose to exclude one or both of them when you ran the patch to upgrade an engine node's Analytics engine to version 15.0. (For more information, see Update AX Server analytic engine to version 15.0.0.)

If you do not want the Python engine or the optional data connectors to be present in the AX Engine Node installation, you can manually remove them.

Remove the Python engine

After upgrading AX Engine Node, on each server where an engine node is installed delete the pyengine folder.

Default location:

C:\ACL\App\analytic_engine\pyengine

Remove the optional data connectors

After upgrading AX Engine Node, on each server where an engine node is installed delete the listed items.

1. On each server where an engine node is installed, navigate to the ACL Connector parent directory.

   Default parent directory location: C:\ACL\ACL Connector

2. Delete these common items:

   • \Common folder

   • cacerts.pem file

3. Delete these connector folders:

   • \ACLAmazonRedshift

   • \ACLCassandra

   • \ACLConcur

   • \ACLCouchbase

   • \ACLDrill

   • \ACLDynamoDB

   • \ACLGoogleBigQuery

   • \ACLHBase

   • \ACLHive

   • \ACLImpala

   • \ACLMongoDB

   • \ACLOracle

   • \ACLSalesForce

   • \ACLSpark

   • \ACLSQLServer

   • \ACLTeradata