Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

Timeout Issue Online - Redshift

Hi there,

 

My dataset is refreshing correctly in Power BI desktop but when I publish it, it fails the scheduled refresh (credentials are working and this is a new issue).

 

Error code 1: 

{"error":{"code":"ModelRefresh_ShortMessage_ProcessingError","pbi.error":{"code":"ModelRefresh_ShortMessage_ProcessingError","parameters":{},"details":[{"code":"Message","detail":{"type":1,"value":"ODBC: ERROR [08S01] [Microsoft][Amazon Redshift] (30) Error occurred while trying to execute a query: [SQLState 08S01] server closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n"}}],"exceptionCulprit":1}}} Table: my_view.

 

Error code 2:

{"error":{"code":"ModelRefresh_ShortMessage_ProcessingError","pbi.error":{"code":"ModelRefresh_ShortMessage_ProcessingError","parameters":{},"details":[{"code":"Message","detail":{"type":1,"value":"Timeout expired. The timeout period elapsed prior to completion of the operation."}}],"exceptionCulprit":1}}} Table: my_view.

 

I have tried to increase the timeout limit of the query by editing the M code to add a 

[CommandTimeout=#duration(0, 1, 0, 0)]

to my M code:

 

let
Source = AmazonRedshift.Database("my_server", "my_db", [BatchSize = null]),

 

but got the following 2 errors:

 

1. Too many arguments, 2-3 arguments expected (I added the CommandTimeout to the end)

2. BatchSize must be specified (I tried changing BatchSize argument to CommandTimeout argument)

 

So how do I increase my timeout? Or do I even need to do this at all - am I barking up the wrong tree?

 

Thanks!

 

 

 

 

  • Hi there

    I would change the Batch Size to be 1000 instead of NULL, so that it can send the data in batches which should make it run faster and not wait for the entire dataset.

3 Replies