On Monday morning one of production staff reported that they cannot input data because the employee data is empty.
I realized this is because MSSQL job failed to run correctly. Quickly I checked the SQL Server management studio, on the history log I found the complete error message was:
Executed as user: Domain\backupexec. SQL Server Network Interfaces: The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you. [SQLSTATE 42000] (Error 848) OLE DB provider “SQLNCLI10” for linked server “servername” returned message “Cannot generate SSPI context”. [SQLSTATE 01000] (Error 7412). The step failed.
Microsoft suggesting below URL to troubleshot cannot generate SSPI context error.
After checking some other experience with this error, I found that the account was locked. It’s true when I checked with Active Directory. After unlock the account. I re-run the SQL job and this time it’s works perfectly.
On this case the error cannot generate SSPI context was because the account that used to connect to the SQL server was locked. Unlocked it from Active Directory was solved the problem.
The server running Ms Windows Server 2008 and Ms SQL Server 2008.