Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
fingerz
Regular Visitor

Data Gateway refresh error: principal name mismatch on certificate

I have a dataset that I currently refresh using my Personal Gateway. My company has now setup a Data Gateway to access the same datasource. When I switch to using the Data Gateway, I get the following error:

 

Something went wrong.
Invalid connection credentials.


Please try again later or contact support. If you contact support, please provide these details.
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 myserver.elcome.ae;DynamicsGPWarehouse.)
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.CredentialError.DataSourceKind: SQL
Microsoft.Data.Mashup.CredentialError.DataSourcePath: myserver.elcome.ae;DynamicsGPWarehouse
Microsoft.Data.Mashup.CredentialError.Reason: PrincipleNameMismatch
Cluster URI: WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activity ID: ff8fc34a-caa1-4b91-7073-6be11094d57b
Request ID: 1ac9b861-2558-ba70-4d30-cec4690dd93b
Time: 2016-08-23 08:26:17Z

 

(server name changed for security reasons)

 

The server has a valid SSL certificate in it's name, so I'm not sure what the issue is here. Any suggestions on why the Personal Gateway is working but the Data Gateway is not with the same data source?

1 REPLY 1
v-qiuyu-msft
Community Support
Community Support

Hi @fingerz,

 

In your scenario, when you configured the data source under the on-premises data gateway, which server name did you specified? I found a similar issue which was fixed by specifying FQDN for SQL Server data source under on-premises data gateway. For more information, please refer to this thread: Certifiticate problem w enterprise gateway import mode, when direct mode works ok.

 

Besides, I would suggest you check which connection string you used in the report to connect to SQL Server. The data source configured under on-premises data gateway needs to use the same connection string.

 

If issue persists, please share on-premises data gateway service logs located at C:\Users\PBIEgwService\AppData\Local\Microsoft\on-premises data gateway\Gateway*.log for our analysis.

 

If you have any question, please feel free to ask.

 

Best Regards,
Qiuyun Yu

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors