Feedback
Did this article resolve your question/issue?

   

Article

Unable to connect after configuring SSL with MongoDB ODBC driver.

Information

 
TitleUnable to connect after configuring SSL with MongoDB ODBC driver.
URL NameUnable-to-connect-after-configuring-SSL-with-MongoDB-ODBC-driver
Article Number000144547
EnvironmentProduct : Progress DataDirect for ODBC for MongoDB driver
Version : 8.0
Database: MongoDB
OS : Windows
Application : All ODBC applications
Question/Problem Description
Connection fails after enabling the SSL on the MongoDB server and ODBC driver side works in non-ssl mode. 
Steps to Reproduce1. Setup a Mongodb server version 3.4.
2. Test connect from ODBC works.
3. Enable SSL on mongodb server side.
4. Start the Mongodb server in ssl mode.
5. Test connect from ODBC side using SSL settings(Security->Encryption method: Change to 1 - Enable SSL
Uncheck the box: Validate Server certificate).
below Error can be seen.
Clarifying Information
Error MessageSQL Engine service could not be reached, falling back to Direct SQL Engine mode.
SSL handshake failed. Remote host closed connection during handshake.
Defect Number
Enhancement Number
Cause
Resolution
Make sure to stop and start the MongoDB ODBC driver service from windows services for new settings to take effect. 
Workaround
Notes
Last Modified Date9/20/2017 11:33 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.