Mongodb Connection failing in June 2020 Patch 10

[Jpatel-Veritone]

From qlik server when I try to test mongoDB connection from ODBC or from qlik web application it gives the error.

ERROR [HY000] [Qlik][MongoDBODBC](110) Error from MongoDB Client: Auth mechanism not specified (Error Code: 11)

It was working fine before the current version I believe.

Qlik is running on Windows Server 2012 R2 Standard
Qlik Sense June 2020 Patch 10
qliksenseserver: 13.82.18

Components used in this product version:

• About Service 1.23.0
• App Migration Service 4.12.0
• Broker Service 5.29.0
• Capability Service 1.7.3
• Client 6.378.17
• Data Preparation Service 2.186.4
• Dependency Graph Service 1.2.0
• Dev Hub 1.14.0
• Download Preparation Service 1.2.5
• Freya Client Service 2.12.0
• Licenses service 3.18.0
• Mobility Registrar Service 1.1.0
• Monitoring Apps 8.6.0
• Natural-language broker, a front-facing API for NL utterances 1.12.0
• Natural-language understanding parser service 0.57.0
• Notifier service 1.1.0
• ODAG Service 3.15.2
• Precedents Service 0.79.0
• Printing Service 15.21.0
• Proxy 13.7.2
• QDC Catalog Service 0.13.0
• QIB Webchat Service 1.5.0
• QIX Engine 12.674.17
• Qlik DataMarket Connector 2.11.0.28
• Qlik Essbase Connector 1.4.0
• Qlik Management Console 1.73.1
• Qlik ODBC Connector 6.49.1
• Qlik REST Connector 2.34.1
• Qlik SalesForce Connector 15.21.0
• Qlik Sense Hub 0.47.9
• Qlik Web Connectors 0.78.0
• Repository 26.19.3
• Scheduler 18.8.3
• Service Dispatcher 15.11.0
• Web Extension Service 1.8.0
• Web Extensions 1.6.0

[Jpatel-Veritone · Accepted solution]

The above error was not coming after adding Auth variables in Advanced Key-Value pair as below
Key                                         Value
SamplingStrategy      Backwards
SamplingStepSize      3

but got new error Error from MongoDB Client: No servers yet eligible for rescan (Error Code: 13053) 

The issue encountered and resolved.
MongoDB server running on London region and the Qlik server running on N.Virginia region.
So issue was with peering connection route table in AWS.

After adding CIDR block of peering (pcx-xxxxxxxx) of VPC in route table it got worked.

So no issue with MongoDB version 4.4.11.

Thanks