Yahoo Web Search

Search results

1. Top results related to the target principal name is incorrect

   • The target principal name is incorrect. Cannot generate SSPI context

     Top Answer

     Answered Jul 02, 2023 · 95 votes

     Try logging out and logging back in again.

     I had this problem with an ASP.NET MVC app I was working on after I changed my Windows password. Relggging fixed it.

     Other Answers

     Answered Dec 09, 2022 · 33 votes

     The SSPI context error definitely indicates authentication is being attempted using Kerberos.

     Since Kerberos authentication SQL Server's Windows Authentication relies on Active Directory, which requires a trusted relationship between your computer and your network domain controller, you should start by validating that relationship.

     You can quickly check that relationship, thru the following Powershell command Test-ComputerSecureChannel.

     Test-ComputerSecureChannel -Verbose-

     If it returns False, you must repair your computer Active Directory secure channel, since without it no domain credencials validation is possible outside your computer.

     You can repair your Computer Secure Channel, thru the following Powershell command:

     Test-ComputerSecureChannel -Repair -Verbose-

     If the above doesn't work (because your domain credentials don't work because the machine isn't trusted) you can use NETDOM RESET instead from an elevated cmd.exe (not PowerShell) prompt:

     NETDOM RESET %COMPUTERNAME% /UserO:domainAdminUserName /Password0:* /SecurePasswordPrompt-

     (Yes, the command-line arguments really do have an O

     (Capital-"Oh", not zero 0

     ). The /Password0:* /SecurePasswordPrompt

     option will use a credential popup instead of having you put your password directly in the command-line, which you must never do).

     Check the security event logs, if you are using kerberos you should see logon attempts with authentication package: Kerberos.

     The NTLM authentication may be failing and so a kerberos authentication attempt is being made. You might also see an NTLM logon attempt failure in your security event log?

     You can turn on kerberos event logging in dev to try to debug why the kerberos is failing, although it is very verbose.

     Microsoft's Kerberos Configuration Manager for SQL Server may help you quickly diagnose and fix this issue.

     Here is a good story to read: http://houseofbrick.com/microsoft-made-an-easy-button-for-spn-and-double-hop-issues/

     Other Answers

     Answered Jan 24, 2018 · 26 votes

     I was getting the same error when trying through windows authentication. Sounds ludicrous but just in case it helps someone else: it was because my domain account got locked somehow while I was still logged in (!). Unlocking the account fixed it.

     Check all answers on Stack Overflow

     1/5

   • The target principal name is incorrect when querying from Azure SQL DB External Table

     Top Answer

     Answered Mar 08, 2023 · 3 votes

     SSL Provider: The target principal name is incorrect.

     signifies that the server name you're using in the connection string does not match a CommonName in the SSL certificate provided by the SQL Server.

     The resolution of the issue is to mention TrustServerCertificate=yes; in the connection string as suggested by AlwaysLearning so it will not check the name of SQL server is matching with CommonName in the SSL certificate provided by the SQL Server.

     I created DataSource with TrustServerCertificate=yes; with below code.

     CREATE EXTERNAL DATA SOURCE DS_External_DB6WITH (TYPE = RDBMS,LOCATION = 'YourServer.database.windows.net;TrustServerCertificate=yes',DATABASE_NAME = 'Database1',CREDENTIAL = DB_scoped_credential5);-

     Execution:

     Check all answers on Stack Overflow

     2/5

   • MSSQL with SSL: The target principal name is incorrect

     Top Answer

     Answered Jul 29, 2016 · 6 votes

     The certificate generated with OpenSSL work properly. In my case the problem was rights of the account under which runs MSSQL over the certificate, I solved this issue with the follow steps:

     • Open SQL Server Configuration Manager.
     • Locate the account which is used to run MSSQL instance (Log On tab on MSSQL instance Properties).
     • Open MMC Console and add Certificates (Local Machine) snap-in.
     • Search the certificate store, right click on certificate and select All Tasks -> Manage Private Keys....
     • Set the Permissions to the same account under which MSSSQL runs.

     Other Answers

     Answered Dec 09, 2022 · 33 votes

     The SSPI context error definitely indicates authentication is being attempted using Kerberos.

     Since Kerberos authentication SQL Server's Windows Authentication relies on Active Directory, which requires a trusted relationship between your computer and your network domain controller, you should start by validating that relationship.

     You can quickly check that relationship, thru the following Powershell command Test-ComputerSecureChannel.

     Test-ComputerSecureChannel -Verbose-

     If it returns False, you must repair your computer Active Directory secure channel, since without it no domain credencials validation is possible outside your computer.

     You can repair your Computer Secure Channel, thru the following Powershell command:

     Test-ComputerSecureChannel -Repair -Verbose-

     If the above doesn't work (because your domain credentials don't work because the machine isn't trusted) you can use NETDOM RESET instead from an elevated cmd.exe (not PowerShell) prompt:

     NETDOM RESET %COMPUTERNAME% /UserO:domainAdminUserName /Password0:* /SecurePasswordPrompt-

     (Yes, the command-line arguments really do have an O

     (Capital-"Oh", not zero 0

     ). The /Password0:* /SecurePasswordPrompt

     option will use a credential popup instead of having you put your password directly in the command-line, which you must never do).

     Check the security event logs, if you are using kerberos you should see logon attempts with authentication package: Kerberos.

     The NTLM authentication may be failing and so a kerberos authentication attempt is being made. You might also see an NTLM logon attempt failure in your security event log?

     You can turn on kerberos event logging in dev to try to debug why the kerberos is failing, although it is very verbose.

     Microsoft's Kerberos Configuration Manager for SQL Server may help you quickly diagnose and fix this issue.

     Here is a good story to read: http://houseofbrick.com/microsoft-made-an-easy-button-for-spn-and-double-hop-issues/

     Other Answers

     Answered Jan 24, 2018 · 26 votes

     I was getting the same error when trying through windows authentication. Sounds ludicrous but just in case it helps someone else: it was because my domain account got locked somehow while I was still logged in (!). Unlocking the account fixed it.

     Check all answers on Stack Overflow

     3/5

   • Error: "The target principal name is incorrect" when attempting to connect to SQL Server

     Top Answer

     Answered Nov 17, 2020 · 4 votes

     Go to Control Panel --> Users Account --> Windows Credentials.

     Make sure you have added the host name / ip address to your hosts file.

     Add a new Windows Credential. For the Internet or network adddress, use the host name that you put into your hosts file, but also append the sql server port number to the end with a colon in between (usually, this is :1433).

     For the Username, prepend the username with the domain name or the workgroup. In my case, it was a workgroup.

     Finally, enter the password associated with the username.

     Check all answers on Stack Overflow

     4/5

   • Also try

     the target principal name is incorrect sql server	2148074274 the target principal name is incorrect
     the target principal name is incorrect outlook	the target principal name is incorrect domain controller
     ssms the target principal name is incorrect	certificate the target principal name is incorrect
     the target principal name is incorrect repl/summary	repadmin the target principal name is incorrect

     5/5

   Show moreShow less

2. learn.microsoft.com › target-principal-name-is-incorrect-when-replicating-dataTarget Principal Name is incorrect when manually replicating data...

   learn.microsoft.com › target-principal-name-is-incorrect-when-replicating-data

   • Cached

   Symptoms. When you use Repadmin.exe or the Active Directory Sites and Services snap-in to manually replicate data between domain controllers, you may receive one of the following error messages: The Target Principal Name is incorrect. Access is denied.

3. stackoverflow.com › questions › 32309922sql server - The target principal name is incorrect. Cannot...

   stackoverflow.com › questions › 32309922

   Aug 31, 2015 · I switched an MS SQL Server instance from running using NT Service\MSSQLSSERVER to running as a Managed Service Account. After doing so, SSMS could connect to the database locally on the server, but not remotely from my laptop. Fixing the SPNs addressed the problem. – Hydrargyrum.

4. stackoverflow.com › questions › 70527434How to fix "The target principal name is incorrect error" with...

   stackoverflow.com › questions › 70527434

   Dec 30, 2021 · The target principal name is incorrect signifies that the Name or IP Address you're using in the Server=...; portion of your connection string does not match a CommonName or SubjectAltName in the X.509 certificate provided by the SQL Server which isn't surprising because, by default, SQL Server installs with a self-signed certificate using only ...

5. learn.microsoft.com › en-us › troubleshootTroubleshoot AD replication error -2146893022 - Windows Server

   learn.microsoft.com › en-us › troubleshoot

   • Cached

   Apr 11, 2024 · This article describes how to troubleshoot a problem in which Active Directory replication fails and generates an error (-2146893022: The target principal name is incorrect). Applies to: Windows Server (All supported versions)

6. stackoverflow.com › questions › 37734311MSSQL with SSL: The target principal name is incorrect

   stackoverflow.com › questions › 37734311

   A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.) (Microsoft SQL Server, Error: -2146893022)

7. learn.microsoft.com › 1368194 › microsoft-sql-the-target-principal-name-is-incorre"Microsoft SQL: The target principal name is incorrect. Cannot...

   learn.microsoft.com › 1368194 › microsoft-sql-the-target-principal-name-is-incorre

   • Cached

   The error message means, you try to logon with Windows Authentication over Kerberos and that fails, because SPN = "Server Principal Name" isn't correctly registered. Ask your IT admin to fix it or use Microsoft® Kerberos Configuration Manager for SQL Server®

8. dba.stackexchange.com › questions › 237737How to resolve an SQL Server "Target principal name is incorrect"...

   dba.stackexchange.com › questions › 237737

   May 9, 2019 · Ensure the Kerberos Service Principal Names are configured correctly, either by giving SQL Server the requisite permissions in Active Directory or by manually configuring them. Take a look at my blog for a quick method of configuring the SPNs that doesn't require rebooting or restarting SQL Server.

9. techcommunity.microsoft.com › t5 › azure-database-support-blogLesson Learned #141: The target principal name is incorrect...

   techcommunity.microsoft.com › t5 › azure-database-support-blog

   • Cached

   Today, I worked on an interesting service request where our customer tried to connect using the FQDN of their private link endpoint - servername.privatelink.database.windows.net and our customer got the error: Error 0 - The target principal name is incorrect. Why? Here we have two issues to explain:

10. dba.stackexchange.com › questions › 241051sql server - The Target Principal Name Is Incorrect. Cannot...

    dba.stackexchange.com › questions › 241051

    Jun 20, 2019 · You will need to create two SPNs for the SQL Server service if the service account does not have permissions to create the SPNs. The following examples assume using the default port of 1433. SetSPN -s "MSSQLSvc/<FQDN_SERVERNAME>" "<DOMAIN>\<SERVICE_ACCOUNT_NAME>".

11. www.sqlservercentral.com › articles › solving-the-target-principal-name-is-incorrectSolving the Target Principal Name is Incorrect - SQLServerCentral

    www.sqlservercentral.com › articles › solving-the-target-principal-name-is-incorrect

    • Cached

    Jun 25, 2002 · One small point to note when we receive the below error while connecting SQL server: The target principal name is incorrect. Cannot generate sspi context.