Forum Discussion
Data Gateway refresh error: principal name mismatch on certificate
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