A customer recently encountered this error with a Dynamics GP eConnect integration:
The target principal name is incorrect. Cannot generate SSPI context.
Just before this error was reported, a new version of a custom Dynamics GP AddIn had been deployed, so I got the support call, as the partner and customer thought the error was released to the new AddIn.
But this error is related to the eConnect user authentication with SQL Server, so deploying a new DLL shouldn't have affected that authentication.
I recommended that the customer's IT team check the status of the eConnect windows service on the terminal server and try restarting it. The eConnect service was running, but when they restarted the service, they received a login error.
It seems that some other process on the client's network was attempting to use the Active Directory account assigned to the eConnect service on the terminal server. That other process, whatever it is, apparently has an invalid or old password for the domain account. So it was failing to login and locking the Active Directory account.
Once the account was locked, the eConnect service on the terminal server would begin receiving the SSPI context errors, as its authentication with SQL Server would fail once the account was locked.
The IT team had previously tried to reset the eConnect account password, but it would just get locked out again by the mystery app or process that was still trying to use the same domain account. So I recommended that they create a new dedicated domain account for use by the eConnect windows service on the terminal server.
Once they setup the new domain account and updated the eConnect windows service to use the new account, the problem went away.
However, this morning the error seemed to occur again, but restarting the eConnect service appears to have resolved it. Given this odd recurrence, there may be some other cause or details that may be contributing to the problem.
Steve Endow is a Microsoft MVP in
Los Angeles. He is the owner of Precipio Services, which provides
Dynamics GP integrations, customizations, and automation solutions.
1 comment:
I recently encountered the same error under equally odd circumstances with eConnect for GP 2016. Although the resolution was unrelated to any AD account issue it took me a while to figure out the problem as there is little to no additional detail behind the error. Needless to say, it would seem that this error is getting generated in a number of situations and they are not necessarily AD related.
Post a Comment