Hi @Anonymous ,
There are a few possible ways to fix this issue, depending on your situation:
- If you are connecting to an Azure SQL Database, you may need to change the compatibility level of the database to 130.
- If you are connecting to a local SQL Server, you may need to enable Named Pipes in the SQL Server Configuration Manager.
- If you are using a domain account to start SQL Server, or when you change the account that is used to start SQL Server, you may need to use the SetSPN.exe utility to control the Service Principal Name (SPN) that is assigned to the service and the account.
- If none of the above methods work, you can try to connect over TCP port and not by instance name. To do this, type into the Server field: {SQL-server-IP}, {SQL-server-port}, for example 192.168.1.5,54222.
You can refer to the following posts that may be helpful to you:
powerbi - The target principal name is incorrect. Cannot generate SSPI context. Azure SQL Database
Getting "Microsoft SQL: The target principal name is incorrect. Cannot generate SSPI context."
Solved: PowerBI Microsoft SQL: The target principal name i... - Microsoft Fabric Community
sql server - How to fix "The target principal name is incorrect error" with Microsoft.Data.SqlClient Version
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
