Issue with Migrating MariaDB Linked Service to Latest Driver in PROD

Question

Issue with Migrating MariaDB Linked Service to Latest Driver in PROD

Loc Nguyen Phuoc Vinh 20

Migrating a MariaDB linked service to use the latest driver as recommended in the documentation: Upgrade the MariaDB Driver Version works fine in lower environments like DEV or UAT, but fails in PROD.

In PROD, the legacy driver still functions correctly. A new linked service was created using the same information as the legacy one (same server, DB name, username, password from Key Vault, and Integration Runtime), but the version with the latest driver fails.

The MariaDB version is verified to be the same across all environments: 10.6.16-MariaDB-log.

The Self-hosted IR version is also the same across all environments: 5.44.8996.4 (Data Factory V2).

Here is the error message received when testing the connection:

User's image

Has anyone encountered this issue before and can provide guidance on how to resolve it?

Pinaki Ghatak 5,690 Reputation points Microsoft Employee Volunteer Moderator

2024-10-21T09:36:50.8133333+00:00
Hello @Loc Nguyen Phuoc Vinh

The error message you shared indicates that the SSL connection could not be established. One possible reason for this issue could be that the latest driver is more strict with SSL connections and requires a higher level of security than the legacy driver.

To resolve this issue, you can try the following steps:

Check the SSL settings on the MariaDB server and make sure they are compatible with the latest driver. You may need to update the SSL settings on the server to support the latest driver.

Check the SSL settings in the connection string used by the linked service. Make sure that the SSL settings are correct and match the settings on the server.

Try disabling SSL in the connection string and see if the connection can be established without SSL. If the connection is successful without SSL, then the issue is definitely related to SSL settings.

If none of the above steps work, you may need to contact MariaDB support for further assistance.

I hope that this response has addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts, but also assist other community members who may be looking for similar solutions.
Loc Nguyen Phuoc Vinh 20 Reputation points

2024-10-21T10:15:17.5466667+00:00

Hi, I did try to disable SSL, but it did work either.
AnnuKumari-MSFT 34,561 Reputation points Microsoft Employee Moderator

2024-11-20T06:59:01.9866667+00:00

Hi Loc Nguyen Phuoc Vinh ,

Just following up to see if the below answer helped. Please do consider clicking Accept Answer as accepted answers help community as well. Also, please click on Yes for the survey 'Was the answer helpful'

Answer accepted by question author

2 additional answers

Your answer

Pinaki Ghatak 5,690 Reputation points Microsoft Employee Volunteer Moderator

2024-10-21T09:36:50.8133333+00:00

Hello @Loc Nguyen Phuoc Vinh

The error message you shared indicates that the SSL connection could not be established. One possible reason for this issue could be that the latest driver is more strict with SSL connections and requires a higher level of security than the legacy driver.

To resolve this issue, you can try the following steps:

Check the SSL settings on the MariaDB server and make sure they are compatible with the latest driver. You may need to update the SSL settings on the server to support the latest driver.

Check the SSL settings in the connection string used by the linked service. Make sure that the SSL settings are correct and match the settings on the server.

Try disabling SSL in the connection string and see if the connection can be established without SSL. If the connection is successful without SSL, then the issue is definitely related to SSL settings.

If none of the above steps work, you may need to contact MariaDB support for further assistance.

I hope that this response has addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts, but also assist other community members who may be looking for similar solutions.
Loc Nguyen Phuoc Vinh 20 Reputation points

2024-10-21T10:15:17.5466667+00:00

Hi, I did try to disable SSL, but it did work either.
AnnuKumari-MSFT 34,561 Reputation points Microsoft Employee Moderator

2024-11-20T06:59:01.9866667+00:00

Hi Loc Nguyen Phuoc Vinh ,

Just following up to see if the below answer helped. Please do consider clicking Accept Answer as accepted answers help community as well. Also, please click on Yes for the survey 'Was the answer helpful'

Answer 1

Hi @Loc Nguyen Phuoc Vinh
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others "I'll repost your solution in case you'd like to accept the answer.
Issue: Migrating a MariaDB linked service to use the latest driver as recommended in the documentation: Upgrade the MariaDB Driver Version works fine in lower environments like DEV or UAT, but fails in PROD.

In PROD, the legacy driver still functions correctly. A new linked service was created using the same information as the legacy one (same server, DB name, username, password from Key Vault, and Integration Runtime), but the version with the latest driver fails.

The MariaDB version is verified to be the same across all environments: 10.6.16-MariaDB-log.

The Self-hosted IR version is also the same across all environments: 5.44.8996.4 (Data Factory V2).

Here is the error message received when testing the connection:

User's image

Has anyone encountered this issue before and can provide guidance on how to resolve it?

Solution: we changed password to something doesn't contain semicolon and we're now able to connect.

this is a confirmed bug from ADF's mariadb driver.

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members

Answer 2

AnnuKumari-MSFT 34,561 Microsoft Employee Moderator

Hi Loc Nguyen Phuoc Vinh ,

Welcome to Microsoft Q&A platform and thanks for posting your query here.

It sounds like you are trying to upgrade the MariaDB driver version for a linked service in Azure Data Factory, but you are encountering an error when testing the connection in the PROD environment. The error message that you are receiving indicates that the connection string is not in the correct format.

Kindly try to switch to 'Password' mode and directly put the password and try testing the linked service if it works fine or not.

If it works fine, kindly create another Secret with the same password in the Key vault and use that one as there could be some unwanted space or character stored in the password of keyvault and the error message could be misleading sometimes.

Similar issue has been faced by customer in the past for PostGreSQL and have been fixed by removing the unwanted character.

Hope it helps. Kindly accept the answer by clicking on Accept answer button. Thankyou

Loc Nguyen Phuoc Vinh 20 Reputation points

2024-10-21T09:20:03.9266667+00:00

Hi,

It’s not the keyvault problem as the existing linked service (using legacy driver) still works.

I create the new linked service using the same configuration as the existing one.
AnnuKumari-MSFT 34,561 Reputation points Microsoft Employee Moderator

2024-10-21T09:39:17.5933333+00:00

Loc Nguyen Phuoc Vinh ,

I understand . Have you migrated the same pipeline from dev to UAT to prod? and facing issue with the prod pipeline or manually created the linked service in prod? If manually created , Kindly just make sure the password entered is correct by revalidating.

You also mentioned , it is working fine with the other environment like dev and test, It means that the issue is not with the new driver but might be with the configuration or infrastructure of prod env. Kindly confirm. Thanks
AnnuKumari-MSFT 34,561 Reputation points Microsoft Employee Moderator

2024-10-22T13:24:18.0066667+00:00

Hi Loc Nguyen Phuoc Vinh ,

Additionally, kindly verify if there are any IP restrictions in the MariaDB server that could be blocking the PROD environment. Also, Kindly ensure the PROD ADF instance and the linked SHIR have proper access to the Key Vault secrets.

Hope it helps. Thankyou
Loc Nguyen Phuoc Vinh 20 Reputation points

2024-11-20T07:30:59.7166667+00:00

Hi @AnnuKumari-MSFT It's not the IP restriction nor the Key Vault access as the legacy linked service still works.
AnnuKumari-MSFT 34,561 Reputation points Microsoft Employee Moderator

2024-11-24T08:22:25.7233333+00:00

Loc Nguyen Phuoc Vinh ,

Thanks for the update. I feel deeper investigation is required for the issue you are facing, would suggest you to open an azure support ticket for the same where dedicated engineers can help you unblock. Thanks
Loc Nguyen Phuoc Vinh 20 Reputation points

2024-11-28T00:55:00.3166667+00:00

I logged a ticket for Azure Support. they said that it's the semicolon in the password caused this problem. I'm trying to change the password to see if it could resolve the issue
AnnuKumari-MSFT 34,561 Reputation points Microsoft Employee Moderator

2024-11-28T04:41:04.55+00:00

Hi Loc Nguyen Phuoc Vinh ,

Thankyou for sharing the update. Kindly try it out and let us know if it worked. Thanks
Loc Nguyen Phuoc Vinh 20 Reputation points

2024-11-29T03:52:16.53+00:00

we changed the password to something that doesn't contain semicolon and able to connect now.

It's a confirmed bug on microsoft driver.

Answer 3

Loc Nguyen Phuoc Vinh 20

we changed password to something doesn't contain semicolon and we're now able to connect.

this is a confirmed bug from ADF's mariadb driver.

Share via

Issue with Migrating MariaDB Linked Service to Latest Driver in PROD

2 additional answers

Your answer