Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Idan_liniad

Refresh keeps failing in MySQL

Submitted by on ‎06-14-2018 05:57 AM

Hey All,

for the last 3 days, I'm having trouble to refresh my dataset.

I keep getting the next error message:

MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
 

 

I'm using on-premises data gateway that installed on Windows Server, that connects to MySQL with "MySQL connector Net".

I have updated the gateway to the last version 14.16.6724.2

 

not sure where to look in the gateway logs in

"C:\Users\PBIEgwService\AppData\Local\Microsoft\On-premises Data Gateway\Gateway*.log".

 

what do I look for? I couldn't find anything suspiciousץ

 

Status: Needs Info
See more ideas labeled with:
5 Comments (5 New)
Comments
v-qiuyu-msft
Community Support
Community Support
‎06-15-2018 12:59 AM

Hi @Idan_liniad,

 

You could search error or exception characters in log files to find the information around the time that issue occurs. You can share gateway log with us to look into it. 

 

When you go to Refresh History on Power BI service, there should be a RequestID and ClusterURI for failed refresh, you can share this information with us as well. 

 

Best Regards,
Qiuyun Yu

Vicky_Song
Impactful Individual
Impactful Individual
‎06-15-2018 01:00 AM
Status changed to: Needs Info
 
Idan_liniad
Frequent Visitor
‎06-17-2018 01:43 AM
Hey Qiuyun Yu, Here are the last 10 failed refresh details from the Refresh History as you asked _________________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 4b3b352e-36d6-48b0-b04a-7cdc038c9a80 Request ID: a2978b21-cd62-691d-fc23-b18c77bc2e6f Time: 2018-06-17 07:09:04Z _________________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 67506b71-def2-4d37-9999-121284da932f Request ID: d8bb761d-7d4e-146d-04f0-c566edb2cc5f Time: 2018-06-17 06:29:34Z ________________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 67506b71-def2-4d37-9999-121284da932f Request ID: 6fa0b05f-f77a-2de8-f5e4-aae2e6b37cd0 Time: 2018-06-17 05:59:02Z _________________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: fade2d20-47ed-73f7-bc57-47252f0622ae Request ID: 476a57e1-aff6-d27a-cd97-7e452f60e875 Time: 2018-06-16 06:58:13Z ________________________________________________________________________________________________ Underlying error code: -2147467259 Table: ⌕ Keywords Stats. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 4b3b352e-36d6-48b0-b04a-7cdc038c9a80 Request ID: 784a5d43-c054-005d-98b2-74d42694714e Time: 2018-06-15 17:10:07Z _______________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 01ce078c-c5f9-4301-ad56-a8eaedc0c076 Request ID: b3b920e4-84ed-8a5b-d9bb-8e99c8624cc4 Time: 2018-06-15 09:31:03Z ______________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: f1df039d-da2b-5bba-efee-d7bb7b3b0852 Request ID: 6ed7d3d5-b5b2-a9b7-2e82-99784faffe8c Time: 2018-06-15 05:31:47Z _______________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 01ce078c-c5f9-4301-ad56-a8eaedc0c076 Request ID: f6cd58a1-9461-c440-65b9-c9dffbc923f6 Time: 2018-06-15 05:17:36Z ______________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 39866f73-3fde-01b2-b758-8b800b602f58 Request ID: 723ea2d0-df9e-468e-1b67-b9a7115ae2f1 Time: 2018-06-14 15:05:40Z _____________________________________________________________________________________________ Underlying error code: -2147467259 Table: Mobile Network. Underlying error message: MySQL: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259 Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net Activity ID: 01ce078c-c5f9-4301-ad56-a8eaedc0c076 Request ID: 22698ed1-181b-425b-a85d-b817f626b6a0 Time: 2018-06-14 10:57:05Z
Idan_liniad
Frequent Visitor
‎06-17-2018 02:04 AM
Hey Again, Here is a link to the logs. the logs are too long to send it here https://drive.google.com/drive/folders/1ZVYv1bVTrlqCbDwk8EDP2eGQEvHvreoO?usp=sharing
Idan_liniad
Frequent Visitor
‎06-18-2018 11:20 PM
Hey Qiuyun Yu, Any insights?
Idea Statuses