Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Datagrace
Starting Member
2 Posts |
Posted - 2010-03-26 : 01:08:35
|
2005, Windows Server 2003. Attempt to login as sa fails first with error 233; subsequently with error 18456. I can get in using Windows authentication. Mixed mode is enabled. I am confident I am using the correct PW. I've not logged into this install for at least 6 months, but have always used sa. Tried stopping re-starting service. Do I have to re-install to re-set the credentials? |
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2010-03-26 : 04:36:41
|
I don't think anyone has all the error codes in memory so it would be really helpful if you posted the error message as well. Is the sa account enabled? Log in with your windows administrator account and run the following:--> EnableALTER LOGIN sa ENABLE--> DisableALTER LOGIN sa DISABLE - LumbagoIf the facts don't fit the theory, change the facts. Albert Einstein |
 |
|
Datagrace
Starting Member
2 Posts |
Posted - 2010-03-26 : 14:19:35
|
Thank you. Error 233:Cannot connect to DELLSERVER.Additional information:A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0- No process is on the other end of the pipe.) (Mircrosoft SQL Server, Error: 233)Error 18456:Loginfailed for user 'sa'. (Microsoft SQL Server, Error: 18456Sa account was enabled-- used it successfully for years. I have now issued the ENABLE command you suggested, stopped and re-started the service, no joy.Local and remote connections are enabled, for TCP/IP only, although I'm only using Management Studio locally.Thank you for your help. I am a Filemaker developer straying from my natural habitat.John WeinshelDatagraceVashon Island, WA |
 |
|
|
|
|
|
|