May 11, 2005 at 7:32 am
Hi,
We have a SQL 7.0 server that just went live after the old one all but died on us. When we switched the machine names we got "Cannot Generate SSPI Context" errors which has caused all sorts of problems. We found a workaround was to use cliconfg on the client machines and add the server name as a named pipe alias - but now we seem to be getting really poor performance and cascading lock issues which we didn't see on the old box. The new box had bigger disks, more memory, better cpu etc etc - so hardware is unlikly to be the issue.
If someone could outline (if there are any) performance issues of using named pipes as opposed to TCP/IP connections then I would be most grateful.
May 11, 2005 at 9:42 am
Can I ask if you have active directory in place because I've seen this a couple of times before and have used the information from the following article to resolve it.
http://www.sqlservercentral.com/columnists/cmiller/cannotgeneratesspicontext.asp
Hope this helps
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply