automated refresh
2 TopicsFailed to connect to AS
I currently have a server running PBIRS Version 1.25.9558.32914 (January 2026), and I'm experiencing this type of error on several dashboards during automatic refreshes. " Failed to connect to AS " What could be the problem? The server resources aren't overloaded, as I've monitored the CPU and RAM usage during these refreshes. What can I check, given that this is happening so frequently?Solved757Views0likes3CommentsScheduled 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>1.1KViews0likes4Comments