'Logon failure: The target account name is incorrect.' She can map drives on other servers, but not on this one. The server is a DC, 2000 server, SP4. We've tried using the FQDN, 'Search for computers' under My network places, adding a network place, browsing the network. Any help would be appreciated. DOes it happen on all User accounts or just one? Have you looked at the Event Logs for any errors? There's a lot of stories about login issues if the time is vastly different on the machines. So before doing anything drastic check the time settings on both machines. Have you tried using the fully qualified.
![Domain join target account name is incorrect Domain join target account name is incorrect](/uploads/1/2/5/4/125481761/196413714.png)
Hello all: I have an Azure SQL server instance up and running- I can connect just fine to it using SSMS. When trying to connect via Power BI Desktop to the same database instance, I'm presented with the following: Details: 'Microsoft SQL: The target principal name is incorrect. Cannot generate SSPI context.' My research on this pointed me to a Kerberos authenticaion issue. Do I need to setup a firewall pinhole (rule) to allow Power BI to make a connection to the SQL server instance? What's causing this error to present and how can I fix it?
Can someone please guide me here? Hello: I have an Azure SQL server instance up and running- I can connect just fine to it using SSMS.
When trying to connect via Power BI Desktop to the same database instance, I'm presented with the following: Details: 'Microsoft SQL: The target principal name is incorrect. Cannot generate SSPI context.'
My research on this pointed me to a Kerberos authenticaion issue. Do I need to setup a firewall pinhole (rule) to allow Power BI to make a connection to the SQL server instance? What's causing this error to present and how can I fix it? Thanks for the guidance. I had the same error when trying to connect to a remote SQL Server. In my case I believe that the error has been caused by cumulative update KB3189866 for Windows 10.
This happened on multiple machines. Uninstalling the update solved the problem.
I have already reported this as a bug to Microsoft Connect. If you think the problem is due to the same conditions you may want to upvote/comment on my report.
Report to Microsoft Connect: Question on Microsoft Forum: Feedback on Feedback Hub: feedback-hub:?contextid=104&feedbackid=903e3ebc-bccb-4b71-8240-7defd6b03fe5&form=1&src=2. Hi, Based on your description, you are connecting to Azure SQL rather than SQL Server on Azure VM, right? If that is the case, what authentication do you use in SSMS and in Power BI Desktop?
The above error occurs when you use integrated Security to connect to SQL Server, for more details, please review this. In your scenario, when connecting to Azure SQL Server from the Power BI Desktop, please ensure firewall rules for the database are configured to ', and you would need to set up a firewall rule to allow Power BI to make a connection.
Also make sure you choose Database authentication mode in Power BI Desktop, and enter server admin account and password rather than AD account to connect to the database. Thanks, Lydia Zhang. Hi, I do have same issue but happening for only one user. Any idea to resolve this issue. Granted permissions to SQL Server, Power BI gateway and Data Connections and able to see power BI gateway from and data connections looks good but not sure why below error message pops up when trying to connect it from Power BI Desktop. Unable to connect We encountered an error while trying to ocnnect.
Details: Microsoft SQL: the target principal name is incorrect. Cannot generate SSPI context.' I would like to let you know what and all steps i tried; Unistall and installed powerBI dataway but no luck. Operating system - Windows 10 upto date. Even i am using windows 10 but able to connect Power BI dekstop successfully with my login but unable to login from his/her credentials. Thanks, Maru.
During Dynamics CRM 2015/2013 setup you might encounter this error in the final system checks process: This is caused due to improper SPN’s ( Service Principal Name) configuration for the SQL server. To resolve this follow these steps: 1. Connect to your SQL server and go to services ( Start - services.msc) from there locate your SQL service and check the Log on account 2.