Alteryx Server Knowledge Base

Definitive answers from Server experts.

How to Prepare for Atlas 4.0 Deprecation

JamesHa
Alteryx Alumni (Retired)
Created

This article will walk through procedures to prepare for the upcoming end of life date for version 4.0 in Mongo Atlas deployments


**All procedures below should be tested in your DEV/SANDBOX environment prior to implementing in PROD**
 

Prerequisites

 
  • Alteryx Server
    • 2020.1 to 2021.3
  • Mongo Atlas
    • 4.0
 

Procedure A (Recommended)

 
  1. Upgrade Alteryx Server to version 2021.4.
  2. Upgrade Mongo Atlas to 4.2.
    1. Up to 4.4.
    2. For 2021.4.
      1. The mongo drivers for this version supports Mongo 4.0, 4.2, and 4.4.
      2. Supported connection string parameters are driver-dependent. Parameters have to be supported by all below-listed supported drivers to be used in a connection string. Supported driver versions include.
        1. c 1.17 (mongoc)
        2. c++ 3.6 (mongocxx)
        3. c# 2.12 (mongoc#)
      3. Links to the Mongo documentation driver support tables are below.
 

Procedure B

 
  1. Stay on the Alteryx Server version you are on.
  2. Test with Atlas 4.2.
    1. If you run into issues submit the problem to Mongo Support and ask for an exception from them to stay on 4.0.
    2. If you do not run into issues and plan to use 4.2, see Procedure C.


Procedure C (Unsupported)

 
  1. Stay on the Alteryx Server version you are on.
  2. Upgrade Mongo Atlas to 4.2.
    1. For 2020.1 - 2021.3.
      1. The mongo drivers for these versions do not support Mongo 4.2 or higher.
      2. Supported connection string parameters are driver dependent. Parameters have to be supported by all below-listed supported drivers to be used in a connection string. Supported driver versions include.
        1. c 1.15 (mongoc)
        2. c++ 3.4.1 (mongocxx)
        3. c# 2.7.2 (mongoc#)
      3. Links to the Mongo documentation driver support tables are below.
 

Common Issues

A known issue can occur with index key names during an Alteryx Server upgrade if following Procedure #3.  If you are on an Alteryx Server version less than 2021.4, running Mongo 4.2 or greater, and then upgrading Alteryx Server, this can occur.

1. Symptoms of this issue.
1. Alteryx Service won't start.
2. Service log error.
1. Mongo error:
 
"Index with name: AS_Applica_1_Type_1_UserName_1_CreationDa_1_Status_1_Owner_1_Completion_1_QOS_Priori_1_AppName_1 already exists with a different name: generic server error" code: <mongodb:85>

2. If you run into this issue please contact Alteryx Support through the case portal or email at support@alteryx.com and a Support Engineer will assist you.

Additional Resources