web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance forum / System.ComponentModel....
Finance forum

System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

(0) ShareShare
ReportReport
Posted on by

We had finished all the steps requested in the document of the deployment successfully, but during the deployment from the lcs we are facing an issue on the synchronization of the data base. Noting that we have double checked the setup and the permission for the user and certificate of the sql server is on all nodes.

we are deploying platform 12 version 7.3

Below is the issue.

---> (Inner Exception #3) System.Data.SqlClient.SqlException (0x80131904): 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.) ---> System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.Dynamics.AX.Deployment.Setup.SqlEditionConnectionScan.IsSqlAzure()

ClientConnectionId:e55211fc-185d-4971-97ee-c8c61dd5173f

Error Number:-2146893022,State:0,Class:20<---

I have the same question (0)
  • Community Member Profile Picture
    on at
    RE: System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

    Hi did you ever manage to find the cause of  this problem? We are having the same error installing on-premises Dynamics after federating the local AD domain with Azure AD

  • Madhan Ramachandran Profile Picture
    30 on at
    RE: System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

    Hi,

    I am also facing the same issue, I have validated certificate instillation and other steps are fine.

    Please provide the resolutions.

    Thanks,

    Madhan

  • Amol@ Profile Picture
    282 on at
    RE: System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

    Hello,

    We also facing the same issue, Is anyone have resolved the same.

    Thanks in Advance,

    Amol

  • Community Member Profile Picture
    on at
    RE: System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

    hii

    thank you for your help we tried the above but still the same error any other solution?

  • Jie G Profile Picture
    on at
    RE: System.ComponentModel.Win32Exception (0x80004005): The target principal name is incorrect

    Hi,

    The error message indicates it should be Kerberos issue regarding SPN(Service Principle Name) with the SQL service. 

    You can refer to the following link about SPN to troubleshoot further:

    https://blogs.msdn.microsoft.com/sqlupdates/2014/12/05/sql-server-kerberos-and-spn-quick-reference/

    https://support.microsoft.com/en-us/help/2443457/you-may-experience-connectivity-issues-to-sql-server-if-spns-are-misco 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Finance

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans