View Only
Expand all | Collapse all

Unable to connect to Informix DB using SSL from

  • 1.  Unable to connect to Informix DB using SSL from

    Posted Tue January 30, 2024 03:34 PM

    We have a .NET Core application that was written quite a while ago that targets .NET Core 3.1. It is using the package to connect to the Informix database.The server database system is an Avaya CMS system, which I believe is running Informix version 14.x and is running on some flavor of Linux. The client applicaiton is running on Windows Server 2022, and runs as a Windows Service. Everything works fine with the application as long as we use Protocol=onsoctcp. However, we have the requirement to connect to the database using TLS 1.2. We understand that this support was added in ibm.csdk.4.50.FC10W1.WIN. We have upgraded the CSDK to use this version, which includes a new version of the dated 9/19/2023 with a File Version of 4.700.7.2021 and a Product Version of 3.1.6. 

    We changed our connection string to the following:

    Database=xxxx;Database Locale=en_us.57372;;Protocol=onsocssl;Password=xxxxxxxx;Server=xxxxxxxx;Service=50001;User ID=xxxxxxx;Pooling=false

    We don't receive any error, but the code just hangs on the Connection Open. Never returns or throws an exception. The Server certificates and CA certificates were loaded into the Trusted Root Certificate Store in Windows Certificate Manager. We can connect to the database using an ODBC connection on the client machine, using protocol onsocssl and the same port. 

    We also tried using the System DSN in the connection string of the Application and we get the same behavior. Just hangs on the IfxConnection.Open.

    Any help would be greatly appreciated. 


    Loyd Vest 

    Loyd Vest

  • 2.  RE: Unable to connect to Informix DB using SSL from

    Posted Tue January 30, 2024 04:56 PM

    We figured out the issue. We were running the Windows Service under the Local Service account, which didn't have the needed permissions. We changed the service to run under an AD account that has elevated privileges, and it fixed the issue. 

    Thanks for your help with this issue. 

    Loyd Vest