Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
10 years ago
Solved

Enterprise gateway "cannot connect to the mashup data source"

Hi, everyone,   I'm having trouble trying to migrate my data sources to the enterprise gateway.   The sql server connections have connected with no issues, however, when I try to connect a Mysql ...
Need Help
  • Anonymous's avatar
    Anonymous
    10 years ago

    I've had the same issue and the fix for me was uninstalling the Personal Gateway or the Enterprise Gateway. I had both running and there seems to be a conflict if both programs are installed.

vyurbonas's avatar
vyurbonas
New Member
6 years ago

PROBLEM

My day started with error during refresh via gateway:

 

{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"An error happened while reading data from the provider: 'Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).'"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"MySql"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath" ...

 

I tried all recomendations above, nothing helped in the begining.

 

STEPS I DID TO SOLVE

  1. Refresh stopped working even from power bi desktop. Got error  
    1. I renewed to Power bi desktop [Version: 2.79.5768.721 64-bit (2020 m. kovas)]    (didn't help)
    2. Added OldGuids=true in  
      • Source = MySQL.Database("xxxxx", "dwhdb", [ReturnSingleDatabase=true,OldGuids=true])   (this solved me refresh in power bi desktop, but refresh via gateway was still failing)
  2. At this moment Refresh via gateway didn't complain about Guid, the error was 
    • {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: Products Data

Finally I remembere doing mysql 8 config changes for ETL tools.

 

[mysqld]
sql_mode=''
character_set_server=utf8mb4
character_set_filesystem=utf8mb4
collation_server=utf8mb4_0900_ai_ci
#character-set-client-handshake=FALSE
init-connect = 'SET NAMES utf8mb4'
innodb_read_io_threads=8
innodb_write_io_threads=8
local_infile=1
disable_log_bin

 

What caused issue for me was character-set-client-handshake=FALSE. I commented it out and it started working again.

I also undone step removed OldGuids=true, which was no longer necessary. And all started working again.

 

CONCLUSION

For me it was caused by MySQL 8 character set configuration. So if you have issue - you may want to revisit your configs of the data source.