Data Refresh with Incremental refresh not working

[VizKid]

Hello...

I am having troble with one of data source I am trying publish on my Premium capacity Workspace!!

I made a regualar dashboard with On-Prem SQL Connnection (worked fine after publishing.. gateway setup via SSO), Now I have new requirment to add incremental refresh so I created new copy in Desktop and adding Parameters + Incremental refresh to Data Set following all the instructions to T and when I publish it and try to refresh.. I get following error.

There was an error when processing the data in the dataset.Hide details
Processing error: COM error: Microsoft.ASWL.Service, An unexpected internal error happened while obtaining the credentials for the data source '<pii>{"protocol":"tds","address":{"server":"prd01","database":"DW"},"authentication":null,"query":null}</pii>': data source information is not found in Power BI service..

Any help would be greatly appreciated.

Thanks so much

[Silke_K]

I learned the hard way that incremental refresh is not working when the data source connection is via Spark to Azure Data Lake. I am not familiar with SSO, and assume that it also one of the data connections that is not set up for IF. Only the more traditional connections are ready for this helpful feature.

[delfinstephan]

Hello, I'm having a similar issue with Data Refresh. When I introduce incremental refresh this is the error I get, and if I choose the normal full on refresh the dataset refreshes within 5 minutes.

Data source error:	{"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":"An error happened while reading data from the provider: 'A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)'"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}}
Cluster URI:	WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID:	c3475bf8-2690-41dc-9ea5-fcfd8663f9b7
Request ID:	6a00130a-2987-5e6f-f6ee-7cfeff9a7047
Time:	2020-07-18 10:37:33Z

[GilbertQ]

Does the user have the right access to query the underlying table?

I would also see who the dataset owner is and make sure that they have got access both in the On-Premise Gateway data source and in the SQL Server.

From your error it appears that is not passing through the right authentication with it being NULL

[VizKid]

Isn't it strange... The error made me think along the same lines...

Yes, I am the Dataset Owner and I can run the Query from the SSMS + I have another dashboard using same connection string and Gateway without any issues.

[GilbertQ]

Does the other dashboard have incremental refresh enabled?

[VizKid]

Hello @GilbertQ 

No, that is only difference... There is no incremental refresh on the other dashboard and that is working with data refreshes,

Thanks

[GilbertQ]

Hi there

I would suggest double checking that the same data source and data source configuration is being used?

[lbendlin]

That doesn't look like a SQL data source. can you show the source query and the incremental refresh settings?