Refresh Errors

[jmiridium]

Keep getting the following errors on three of the four datasets:

Data source error:	Unable to refresh the model (id=2624126) because it references an unsupported data source.
Cluster URI:	WABI-WEST-US-redirect.analysis.windows.net
Activity ID:	51fd3ab6-9128-f4a9-d93e-bd04ff1a9293
Request ID:	85bd27f5-8954-6927-7631-c32190058c90
Time:	2017-06-12 19:23:50Z

These all test fine under the Test All Connections everything works fine. How can I address this issue?

[jmiridium]

It should be noted that the data source on all of these are SQL Server

[Anonymous]

Download your file as a PBIX and post a screenshot of the "Data Source Settings", which is found under "Edit Queries".  Check each one and make sure it is a supported format.

[jmiridium]

Scheduled refresh failed:

Technical Information:

Activity Id: a319e512-09d8-4cae-a7fa-057ba410ede0

Request Id: 0c8f9e3f-991e-4f10-bfb1-e9c2792fe21a

Cluster Name: WABI-WEST-US-redirect.analysis.windows.net

Refresh Start Time: 06/13/2017 04:00:01Z

Refresh End Time: 06/13/2017 04:02:36Z

But the manual refresh worked:

[jmiridium]

Datasource settings:

[jmiridium]

Just did a refresh and got a new errror:

Underlying error code:	-2147467259
Underlying error message:	The server name provided doesn't match the server name on the SQL Server SSL certificate. Please see https://go.microsoft.com/fwlink/?LinkId=394782. (Source at entsccm03;CM_IRD.)
DM_ErrorDetailNameCode_UnderlyingHResult:	-2147467259
Microsoft.Data.Mashup.CredentialError.DataSourceKind:	SQL
Microsoft.Data.Mashup.CredentialError.DataSourcePath:	entsccm03;CM_IRD
Microsoft.Data.Mashup.CredentialError.Reason:	PrincipleNameMismatch
Microsoft.Data.Mashup.MashupSecurityException.DataSources:	[{"kind":"SQL","path":"entsccm03;CM_IRD"}]
Microsoft.Data.Mashup.MashupSecurityException.Reason:	PrincipleNameMismatch
Cluster URI:	WABI-WEST-US-redirect.analysis.windows.net
Activity ID:	7f6fe60b-755c-2219-f3d3-7a9dffe23615
Request ID:	f1284a24-c195-bb3d-1d57-baae1dccb388
Time:	2017-06-13 14:29:04Z

[jmiridium]

It also seems support.powerbi.com isn't a good source for getting help with issues such as this

[v-qiuyu-msft]

Hi @jmiridium,

In your scenario, please modify the .pbix file to set the data source use the FQDN of the server. If you also configure the dataset use the data gateway, please create a data source under data gateway use the FQDN of the server. See: Troubleshooting the On-Premises Data Gateway.

By the way, please try to update the gateway to the latest version.

Best Regards,
Qiuyun Yu

[jmiridium]

Why did this change? It was woring without FQDN? Also other reports are working fine without FQDN

[v-qiuyu-msft]

Hi @jmiridium,

Regarding the error "The server name provided doesn't match the server name on the SQL Server SSL certificate", you can see below information from here.

This can occur when the certificate CN is for the servers fully qualified domain name (FQDN) but you only supplied the netbios name for the server. This will cause a mismatch for the certificate. To resolve this issue, you will need to make the server name within the gateway data source, and the PBIX file, to use the FQDN of the server.


So I suggest you specify the server name use FQDN of the server.

Best Regards,

Qiuyun Yu

[jmiridium]

Any ideas?