Re: Cannot generate SSPI Context error

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

Date: Sun, 31 Oct 2004 05:04:01 -0800

No, I haven't run SQL Server Profiler. Do I have it on MDSE?

"Uri Dimant" wrote:

> Peter
> Perhaps it is because ADO.NET keeps pool connection by default. Have you ran
> SQL Server Profiler?
>
> "Peter B.L. Rasmussen" <PeterBLRasmussen@discussions.microsoft.com> wrote in
> message news:422DFB2A-B95E-4309-B43A-5BD64EBDC093@microsoft.com...
> > It happens Client-Side, in my application (VB.NET), when I am not working
> in
> > the application for some time. Then when the application (or the IDE)
> tries
> > to open a connection, it happens. If I keep the connection "alive" by
> working
> > in the application (or in the development IDE), it does not happen.
> >
> > Peter
> >
> > "Uri Dimant" wrote:
> >
> > > Peter
> > > Where did it happen in an application or when you log in in EM/QA?
> > > If it happend on ther client side , so perhaps some piece of code
> closes
> > > connection. Can you run SQL Server Profiler to capture what is going on
> > > during a half-two hours?
> > >
> > >
> > >
> > >
> > >
> > > "Peter B.L. Rasmussen" <PeterBLRasmussen@discussions.microsoft.com>
> wrote in
> > > message news:8C22E3CE-23E5-48AB-A30B-22A0506829E2@microsoft.com...
> > > > 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
> > > >
> > >
> > >
> > >
>
>
>