Forum Discussion
Scheduled Refresh Fails, Manual Refresh Succeeds
I have a Semantic Model that utilizes 5 data sources. One of the data sources (connected to Amazon Redshift SQL) keeps triggering a failure message 3-5 minutes into the scheduled refresh (error at the bottom of post).
When I go into the connection settings, I see the password is reduced down to 8 characters (this might just be a visual thing, but either way). I then put the password in, Save, and trigger a refresh on the server again. This refresh always works. I've also tried making a new connection and replacing he existing one - same error occurs. So either the data source can't support scheduled refreshes or the correct password won't save. Has this happened to anyone else out there? Any ideas how to restore the automation to my refresh?
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
[ValidateMarkupTags]<ccon>{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"[ccon][ccon]ODBC: ERROR [08S01] [Microsoft][Amazon Redshift] (10) Error occurred while trying to connect: [SQLState 08S01] connection to server at \"[SERVER STRING IS HERE]" ([ccon]<ip>52.26.233.171</ip>[/ccon]<ip><ip>52.26.0.0</ip></ip>), port 5439 failed: timeout expired\n[/ccon][/ccon]"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10478"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"AmazonRedshift"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"[ccon]etl-workgroup.774598924186.us-west-2.redshift-serverless.amazonaws.com;bswift[/ccon]"}},{"code":"Microsoft.Data.Mashup.ValueError.NativeError","detail":{"type":1,"value":"10"}},{"code":"Microsoft.Data.Mashup.ValueError.OdbcErrors","detail":{"type":1,"value":"#table({\"SQLState\", \"NativeError\", \"Message\"}, {})"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.SQLState","detail":{"type":1,"value":"08S01"}}],"exceptionCulprit":1}}}</ccon>
4 Replies
Please confirm if your issue is related to Report Server.
Hi palmersong ,
Thank you for reaching out to the Microsoft Community Forum.
Please try below things to fix the issue.
1. Check Data Source Credentials, Open Report Manager. Go to your report --> Manage --> Data Sources. check Credentials stored securely in the report server is selected. Re-enter the Redshift username and password here, not just in Power BI Desktop. Test the connection.2. Verify Service Account Permissions, The Power BI Report Server service account must have access to Redshift. If Redshift is in AWS VPC, whitelist the Report Server machine’s IP in the Redshift security group.
3. In the RSReportServer.config file, you can increase the DatabaseQueryTimeout setting. Default is often 120 seconds; increase to 300 or more if queries are large.
4. Please check port 5439 is open from the Report Server machine to Redshift. If using SSL, confirm the certificate settings match what you use in Desktop.
5. Report Server uses the ODBC driver installed on the machine. Make sure the Amazon Redshift ODBC driver is up to date and configured correctly.
6. If you use Execution Account in Report Server, ensure it has proper permissions and network access.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Yes, this issue is related to the Report Server and not my local PowerBI. I've passed along the note above to my system admin, but I don'thave access to do any of those things so I need to wait to hear back from him and will report back. Thank you!
Hi palmersong ,
Thank you for the update. As you mentioned in your previous post, you are checking with your system admin.
Once you got update, please do let us know.
Regards,
Dinesh
