# Microsoft SQL Server Connector Connection Issue

**URL:** <https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security\
**Created:** [April 15, 2024, 3:38pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614 "2024-04-15T15:38:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![adyer](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@adyer](https://developer.sailpoint.com/discuss/u/adyer)\
**Post date:** [April 15, 2024, 3:38pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614/1 "2024-04-15T15:38:34Z")

</div>

Hi Team,

We configured Microsoft SQL Server Connector in our Identitynow tenant and imported the proper jre files as per sailpoint documentation. Our firewall access is also allow, however when we hit on test connection we get the following error message: We are using a SQL Authentication to connect.

Error Received:

[ConnectorException] [Error details] The server encountered an unexpected error while contacting target system. Please check the logs. “encrypt” property is set to “true” and “trustServerCertificate” property is set to “false” but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 ![image](https://global.discourse-cdn.com/sailpoint/original/2X/3/3cd43040865a9bdbcac819d85b988a09e8a35b26.png)

---

<div class="post-metadata">

**Author:** ![ipobeidi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ipobeidi/32/16000_2.png) [@ipobeidi](https://developer.sailpoint.com/discuss/u/ipobeidi)\
**Post date:** [April 15, 2024, 4:17pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614/2 "2024-04-15T16:17:04Z")

</div>

Check the JDBC query , if the encrypt variable is set to true.

If you wanna use SSL , you need to import the Certificate of the DB to tha keystore of the VA.

Best!

---

<div class="post-metadata">

**Author:** ![adyer](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@adyer](https://developer.sailpoint.com/discuss/u/adyer)\
**Post date:** [April 15, 2024, 4:24pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614/3 "2024-04-15T16:24:45Z")

</div>

@ipobeidi this the jdbc query that i’m using.  
jdbc:sqlserver://dummy:1433;databaseName=testdb;

---

<div class="post-metadata">

**Author:** ![ipobeidi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ipobeidi/32/16000_2.png) [@ipobeidi](https://developer.sailpoint.com/discuss/u/ipobeidi)\
**Post date:** [April 15, 2024, 7:51pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614/4 "2024-04-15T19:51:24Z")

</div>

changed it to this

jdbc:sqlserver://dummy:1433;databaseName=testdb;encrypted=false;trustServerCertificate=true;

---

<div class="post-metadata">

**Author:** ![adyer](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@adyer](https://developer.sailpoint.com/discuss/u/adyer)\
**Post date:** [April 16, 2024, 9:43pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614/5 "2024-04-16T21:43:11Z")

</div>

thanks that did the trick.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [June 15, 2024, 9:43pm UTC](https://developer.sailpoint.com/discuss/t/microsoft-sql-server-connector-connection-issue/50614/6 "2024-06-15T21:43:21Z")

</div>

Closed on June 15, 2024, 9:43pm UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.