Cannot generate SSPI Context error

From: Peter B.L. Rasmussen (PeterBLRasmussen_at_discussions.microsoft.com)
Date: 10/31/04 

Date: Sun, 31 Oct 2004 02:49:01 -0800

I have a recurring problem with the "Cannot generate SSPI context" error. It
works fine for some time, but then it stops working. Generally after half an
hour - two hours time. A logoff/logon always fixes the problem.
I have reviewed the 811889 article, but this doesn't help me. The connection
to the SQL server works fine, but at some time it is like the user looses his
credentials and then can't connect and SSPI won't reconnect him.

Some basic info:
Server is Windows 2000 server SP1 with AD. (was SP4 earlier, with the same
problem, so upgrading to SP4 will not solve the problem by itself. The server
has just been reinstalled from scratch, not finished SPs and updates yet)
SQL Server is MSDE, client logging on with NT security, SQL Server is
installed on the same physical server as the domain controller (only one
domain controller exists)
Client is XP PRO, same problem with SP2 or without SP2
User on client is logged on to domain with Admin+Domain admin privileges
Problem does not exist if client does not log on to domain

Anybody got any ideas on how to solve this problem?

Peter

Relevant Pages

  • Re: Cannot generate SSPI Context error
    ... If it happend on ther client side, so perhaps some piece of code closes ... Can you run SQL Server Profiler to capture what is going on ... > to the SQL server works fine, but at some time it is like the user looses ... > installed on the same physical server as the domain controller (only one ...
    (microsoft.public.sqlserver.security)
  • Re: Connection dropouts
    ... "The solution was to fully qualify the server that was being accessed. ... > The client application, from what I can tell, is a VB ... > to check the pc's ability to connect to the SQL Server. ... > message that says 'Cannot generate SSPI context'. ...
    (microsoft.public.sqlserver.clients)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)