Re: help me! :(

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 04/02/04 

Date: Fri, 02 Apr 2004 09:36:58 -0700

Check the following Knowledge Base article:
Missing Windows NT LM Security Support Provider registry key
causes "Cannot Generate SSPI Context" error message when you
connect to SQL Server
http://support.microsoft.com/?id=269541

-Sue

On Fri, 2 Apr 2004 08:25:51 -0800, "amichaud"
<anonymous@discussions.microsoft.com> wrote:

>We get the following error: Connection Failed:
>SQLState: 'HY000' SQL Server Error:
>1060 [microsoft][ODBC SQL Server Driver]Connot generate
>SSPI Context Anybody ...
>
>
>client: nt4 workstation
>server: windows 2000 , sql server 7.x

Relevant Pages

  • Re: SSPI Context problem
    ... 269541 Missing Windows NT LM Security Support Provider registry key causes ... "Cannot Generate SSPI Context" error message when you connect to SQL Server ...
    (microsoft.public.sqlserver.programming)
  • Re: Trying to find the connection source
    ... John Doe wrote: ... How to troubleshoot the "Cannot generate SSPI context" error message ... Source = Microsoft OLE DB Provider for SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Cannot initialize SSPI package
    ... Are you able to connect with SQL Server authentication? ... Troubleshoot the "Cannot Generate SSPI Context" Error Message ...
    (microsoft.public.sqlserver.security)
  • Re: Trying to find the connection source
    ... How to troubleshoot the "Cannot generate SSPI context" error message ... Source = Microsoft OLE DB Provider for SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Cannot generate SSPI context
    ... There's a good article on troubleshooting this issue here ... Troubleshoot the "Cannot Generate SSPI Context" Error Message ... Jasper Smith (SQL Server MVP) ...
    (microsoft.public.sqlserver.security)