I have a small farm installation of MOSS. I have a back-end server, front-end server and my database server (Microsoft SQL 2005). Everything is working great except the odd time I get the error Cannot generate SSPI context on my website. It seems like this is happening almost every 12 hours. Has anyone else had a similiarproblem?

Have you implemented any solutons/webparts that are NOT standard sharepoint ? Kind regards, Eric van GlabbeekWilling to learn everything about Sharepoint there is to learn. My blog

Everything I have on my site is standard SharePoint except for my menu is using CSS Friendly Control Adapter. My site crashed again last night. Here were the errors before it crashed. Event Type: ErrorEvent Source: UserenvEvent Category: NoneEvent ID: 1053Date: 30/10/2009Time: 1:11:22 AMUser: NT AUTHORITY\SYSTEMComputer: SPFEDescription:Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. -------------------------------------------------------------- Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: General Event ID: 27745Date: 30/10/2009Time: 1:25:15 AMUser: N/AComputer: SPFEDescription:The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_Config on mydbserver.com. Check the database connection information and make sure that the database server is running.. -------------------------------------------------------------- Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: Database Event ID: 5586Date: 30/10/2009Time: 1:25:28 AMUser: N/AComputer: SPFEDescription:Unknown SQL Exception 0 occured. Additional error information from SQL Server is included below.Cannot generate SSPI context. -------------------------------------------------------------- Event Type: ErrorEvent Source: Windows SharePoint Services 3Event Category: Timer Event ID: 6398Date: 30/10/2009Time: 1:25:30 AMUser: N/AComputer: SPFEDescription:The Execute method of job definition Microsoft.SharePoint.Administration.SPConfigurationRefreshJobDefinition (ID f271a8eb-e559-4b9e-a648-ed8275940f47) threw an exception. More information is included below.Cannot generate SSPI context.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Hi, The following article describe how to troubleshoot the most typical sources of the "Cannot generate SSPI context" error message. You may receive this error message under the following conditions: You are connecting to SQL Server. You are using Integrated Security. Kerberos is used to perform the security delegation. How to troubleshoot the "Cannot generate SSPI context" error message http://support.microsoft.com/kb/811889 Hope this helps.Rock Wang MSFT

I had a similar issue while transferring a content DB to a new SQL server. The source SQL server was a Windows 2003 with SQL 2005 system the destination server is running Windows 2008 R2 with SQL 2008 R2. My SharePoint server is running Windows 2003 SP2 with SharePoint 2007 SP2. --- From KB 977321 --- In the Group Policy Management Console (GPMC), locate the following location: Computer Configuration\ Windows Settings\ Security Settings\ Local Policies\ Security Options Click to select the Network security: Configure encryption types allowed for Kerberos option. Click to select Define these policy settings and all the six check boxes for the encryption types. Click OK. Close the GPMC. -------------- Good luck The problem had to do with encryption providers for the Kerberos process, on the 2008 R2 system we had to enable all of the available encryption providers for Kerberos to get past the SSPI context issue. See: http://support.microsoft.com/kb/977321/ not directly related to SQL or SharePoint but this did resolve the issue.

It looks that this exception is general error for several problems, in our case it was because the client computer had a different date than the sql server computer, making the dates equal fixed the problem.