Cannot generate SSPI context
I have a SQL Server 2000 in a specific W2K server, that belongs to a domain that is administered by a W2003 server.
There is a client that has a new computer with WXP in the same domain. It used to have an old machine with W2K pro. and with the same user it worked OK.
When accesing SQL from the client with an Office2003 application via ODBC with windows authentication, after several minutes working OK, suddenly it gets this message:
Conection error. SQL state: S1000
Cannot generate SSPI context.
In the client I have executed cliconfg.exe and created a piped name protocol, but still it won't work.
Risposte
(1) Is this a remote server or local server?
(2) Are you using domain account for login or machine local account?
(3) Can you try to logout and login back in to see if it works again?
On your server go to Start>Programs>Microsoft SQL Server 2005>SQL Configuration Manager
In the left hand window expand the tree next to SQL Server Database Services and enable Named Pipes and try to connect
If it is still failing try this:
On your desktop go to Start>Run and type cmd and hit enter
At the command prompt type Cliconfg.exe and hit enter
When the utility box pops up click on the Alias tab and create a new alias by typing in your server name and click OK, then try to connect again.
You should not have to create any Protocols to make it work.
Tutte le risposte
(1) Is this a remote server or local server?
(2) Are you using domain account for login or machine local account?
(3) Can you try to logout and login back in to see if it works again?
On your server go to Start>Programs>Microsoft SQL Server 2005>SQL Configuration Manager
In the left hand window expand the tree next to SQL Server Database Services and enable Named Pipes and try to connect
If it is still failing try this:
On your desktop go to Start>Run and type cmd and hit enter
At the command prompt type Cliconfg.exe and hit enter
When the utility box pops up click on the Alias tab and create a new alias by typing in your server name and click OK, then try to connect again.
You should not have to create any Protocols to make it work.
I resolved my issue by noticing that the Server Network Utility had a Port address of 1533 verse 1433. After changing the port to 1433 it worked. (After a restart of the service)
I made the following additional changes before testing. I don't believe they contributed to the fix but here it is:
- Sequence for both client and server network protocols is Named Pipes and then TCP/IP
- Removed redundant alias (original name and alias were identical...duh)
- This is great, finally over several sleepless nites thinking about why
does this problem all of a sudden appeared when I have been able to
access it before.
Anyway after using cliconfg.exe and set the alias of my SQL server 2000 host name and the protocol to name piped, which is running separately on a Win2003 SE and is sitting in a WORKGROUP.
My client is a SQL 2005 Management Studio Express.
