Microsoft Integration Runtime Configuration Manager returns "internal client error" when connecting to MySQL

Question

Microsoft Integration Runtime Configuration Manager returns "internal client error" when connecting to MySQL

Roust_m 1

Hi,

I've built few new VMs in AWS and installed Microsoft Integration Runtime Configuration Manager. On some of them it works fine, on others it returns:
"[Microsoft][MySQL] (42) Internal client error.
ERROR [HY000] [Microsoft][MySQL] (42) Internal client error."

The connection to the same MySQL server works fine on the same box if I use ODBC Data Source Administrator (64 bit).

Any ideas?

Thanks.

PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-15T08:27:10.563+00:00

Hello @Roust_m ,

Welcome to the Microsoft Q&A platform.

In order to investigate further, I would request you to share the complete stack trace of the error message which you are experiencing along with the screenshot?
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-16T11:49:22.5+00:00

Hello @Roust_m ,

Just checking in if you have had a chance to see the previous response. We need the following information to understand/investigate this issue further.
Roust_m 1 Reputation point

2021-02-17T07:20:10.95+00:00

Sorry, please find attached.69024-runtimelog-small.xml
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-18T10:02:08.217+00:00

Hello @Roust_m ,

Thanks for sharing the logs. We are investigating the issue and we will share our findings soon.
Roust_m 1 Reputation point

2021-02-19T03:45:07.29+00:00

And the screenshot
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-22T08:27:24.233+00:00
Hello @Roust_m ,

Could you please share the driver logs to further investigation?

Here are the steps to collect the logs:

Step1: Set up a self-hosted IR and enable logging on it:
Change the content of <IR Installation Path>\Shared\ODBC Drivers\Microsoft {connector name} ODBC Driver\lib\microsoft.{connector name}odbc.ini to below to enable logging:

[Driver] ErrorMessagesPath=..\ErrorMessages LogLevel=6 LogPath=<Log Path> LogType=FILE

The <Log Path> is an absolute path to a folder on the machine where IR is installed, for example: D:\log{connector name}.

Step2: After logging is enabled, please recreate the linked service depended on self-host IR and reload the tables again. The IR logs will be created under <Log Path>. After got the logs, please send them to us.

Step3: Disable IR logging by changing back the content of the microsoft.{connector name}odbc files.
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-22T08:28:41.977+00:00
Hello @Roust_m ,

Additional to above response:

Important notes while gathering the logs:

The log path has to be created before logging.

Please do not specify a log path under C:\ since the IR may not have permission to create log files under that path.

Please make sure you have reviewed the log files and removed all secrets before sending the files to us.
KranthiPakala-MSFT 45,982 Reputation points Microsoft Employee

2021-02-23T09:10:23.797+00:00

Hello @Roust_m ,

As requested by Pradeep, have you got a chance to gather the driver logs? If so could you please share with us so that we can work with internal team to better assist on this issue.

We look forward to your response.

Thank you

PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-15T08:27:10.563+00:00

Hello @Roust_m ,

Welcome to the Microsoft Q&A platform.

In order to investigate further, I would request you to share the complete stack trace of the error message which you are experiencing along with the screenshot?
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-16T11:49:22.5+00:00

Hello @Roust_m ,

Just checking in if you have had a chance to see the previous response. We need the following information to understand/investigate this issue further.
Roust_m 1 Reputation point

2021-02-17T07:20:10.95+00:00

Sorry, please find attached.69024-runtimelog-small.xml
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-18T10:02:08.217+00:00

Hello @Roust_m ,

Thanks for sharing the logs. We are investigating the issue and we will share our findings soon.
Roust_m 1 Reputation point

2021-02-19T03:45:07.29+00:00

And the screenshot
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-22T08:27:24.233+00:00

Hello @Roust_m ,

Could you please share the driver logs to further investigation?

Here are the steps to collect the logs:

Step1: Set up a self-hosted IR and enable logging on it:
Change the content of <IR Installation Path>\Shared\ODBC Drivers\Microsoft {connector name} ODBC Driver\lib\microsoft.{connector name}odbc.ini to below to enable logging:

[Driver] ErrorMessagesPath=..\ErrorMessages LogLevel=6 LogPath=<Log Path> LogType=FILE

The <Log Path> is an absolute path to a folder on the machine where IR is installed, for example: D:\log{connector name}.

Step2: After logging is enabled, please recreate the linked service depended on self-host IR and reload the tables again. The IR logs will be created under <Log Path>. After got the logs, please send them to us.

Step3: Disable IR logging by changing back the content of the microsoft.{connector name}odbc files.
PRADEEPCHEEKATLA-MSFT 70,656 Reputation points Microsoft Employee

2021-02-22T08:28:41.977+00:00

Hello @Roust_m ,

Additional to above response:

Important notes while gathering the logs:

The log path has to be created before logging.

Please do not specify a log path under C:\ since the IR may not have permission to create log files under that path.

Please make sure you have reviewed the log files and removed all secrets before sending the files to us.
KranthiPakala-MSFT 45,982 Reputation points Microsoft Employee

2021-02-23T09:10:23.797+00:00

Hello @Roust_m ,

As requested by Pradeep, have you got a chance to gather the driver logs? If so could you please share with us so that we can work with internal team to better assist on this issue.

We look forward to your response.

Thank you

Answer 1

Roust_m 1

Hi, apologies for the delay, attaching the logs.78971-microsoftmysqlodbcdriver.log 78809-microsoftmysqlodbcdriver-connection-0.log

Answer 2

Roustam Akhmetov 1

We found a workaround, by disabling a windows firewall you can make it work on this particular server. Other servers do not require firewall to be disabled to make it work. Wondering what port (or ports) should I allow to keep the firewall running and the connectivity working?

Microsoft Integration Runtime Configuration Manager returns "internal client error" when connecting to MySQL

2 answers

Activity