Good afternoon,
I'd been asked by one of our users to enable mixed-mode logins on his laptop's SQL Server (sandbox server). Having done that, I attempted to log in via the 'sa' account to verify, but ran into an issue. The basic config settings are below, followed by the startup log info, and finally the actual problem is at the bottom of the post.
=========================================
==============CONFIGURATION==============
=========================================
**These are the *enabled* settings**
Surface Area Configuration
--Local and remote connections
----Using TCP/IP only
SQL Server configuration Manager
--Protocols for MSSQLSERVER
----Shared Memory
----TCP/IP
--Client Protocols
----Shared Memory
----TCP/IP
SSMS
--Server Properties
----Security
------SQL Server and Windows Authentication mode
----Connections
------Allow remote connections to this server
--Login Properties - sa
----Both enforcement options *unchecked*
----Default database - master
----Status
------Permission to connect - Grant
------Login - Enabled
=========================================
===============STARTUP LOG===============
=========================================
2009-09-08 14:29:36.82 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2009-09-08 14:29:36.82 Server (c) 2005 Microsoft Corporation.
2009-09-08 14:29:36.82 Server All rights reserved.
2009-09-08 14:29:36.82 Server Server process ID is 2188.
2009-09-08 14:29:36.82 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-09-08 14:29:36.82 Server This instance of SQL Server last reported using a process ID of 5300 at 9/8/2009 2:29:31 PM (local) 9/8/2009 6:29:31 PM (UTC). This is an informational message only; no user action is required.
2009-09-08 14:29:36.82 Server Registry startup parameters:
2009-09-08 14:29:36.84 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-09-08 14:29:36.84 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-09-08 14:29:36.84 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-09-08 14:29:36.91 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-09-08 14:29:36.91 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-09-08 14:29:38.77 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-09-08 14:29:39.24 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-09-08 14:29:41.29 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-09-08 14:29:41.37 Server Database Mirroring Transport is disabled in the endpoint configuration.
2009-09-08 14:29:41.55 spid5s Starting up database 'master'.
2009-09-08 14:29:42.13 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-09-08 14:29:42.60 spid5s SQL Trace ID 1 was started by login "sa".
2009-09-08 14:29:42.74 spid5s Starting up database 'mssqlsystemresource'.
2009-09-08 14:29:43.58 spid9s Starting up database 'model'.
2009-09-08 14:29:43.60 spid5s Server name is 'TANDEL-47'. This is an informational message only. No user action is required.
2009-09-08 14:29:43.76 Server Error: 17190, Severity: 16, State: 1.
2009-09-08 14:29:43.76 Server FallBack certificate initialization failed with error code: 1.
2009-09-08 14:29:43.80 Server Warning:Encryption is not available, could not find a valid certificate to load.
2009-09-08 14:29:43.83 Server Server is listening on [ 'any' <ipv4> 1433].
2009-09-08 14:29:43.83 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2009-09-08 14:29:43.83 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-09-08 14:29:43.83 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2009-09-08 14:29:43.83 Server Dedicated admin connection support was established for listening locally on port 1434.
2009-09-08 14:29:43.83 spid9s Clearing tempdb database.
2009-09-08 14:29:43.91 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-09-08 14:29:44.79 spid13s Starting up database 'msdb'.
2009-09-08 14:29:44.79 spid15s Starting up database 'eVisioning4.3'.
2009-09-08 14:29:44.79 spid14s Starting up database 'ReportServerTempDB'.
2009-09-08 14:29:44.79 spid12s Starting up database 'ReportServer'.
2009-09-08 14:29:47.49 spid9s Starting up database 'tempdb'.
2009-09-08 14:29:49.23 spid12s The Service Broker protocol transport is disabled or not configured.
2009-09-08 14:29:49.24 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-09-08 14:29:50.40 spid12s Service Broker manager has started.
2009-09-08 14:29:51.35 spid15s CHECKDB for database 'eVisioning4.3' finished without errors on 2009-08-09 00:00:08.340 (local time). This is an informational message only; no user action is required.
2009-09-08 14:29:51.43 spid5s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2009-09-08 14:29:51.43 spid5s Recovery is complete. This is an informational message only. No user action is required.
=========================================
==========DESCRIPTION OF PROBLEM=========
=========================================
*Note* all connection attempts are being made inside SSMS.
When connecting through Windows Authentication, I can log in just fine using my domain account. When I attempt to log in through the SQL Server "sa" account, I get the following message:
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.) (Microsoft SQL Server, Error: 233)
This corresponds with the following entry in the log:
2009-09-08 14:33:52.69 Logon Error: 18456, Severity: 14, State: 8.
2009-09-08 14:33:52.69 Logon Login failed for user 'sa'. [CLIENT: <local machine>]
If I specify in the connection dialog to explicitly use TCP/IP, instead of the above message, I simply get the same "login failed" entry as the logfile (minus the State 8 info).
Now, I know that State 8 typically means a password mismatch, however I went in early on in the troubleshooting process and changed the password to the letter 'a' for the purpose of eliminating any possible mistypes. I am 100% certain the password I'm entering is correct.
I can log in via the 'osql' shell command without any problems.
The problem only seems to crop up when using the SSMS app (installed on the same machine as the SQL Server).
Additionally, I tried creating a new user and logging in through it. Same problem as 'sa'.
I've tried just about every reasonable combination of settings I can think of. I don't use SQL Server myself, so I'm running out of ideas on where to go from here.
Thoughts?
--Zack Townsend
I'd been asked by one of our users to enable mixed-mode logins on his laptop's SQL Server (sandbox server). Having done that, I attempted to log in via the 'sa' account to verify, but ran into an issue. The basic config settings are below, followed by the startup log info, and finally the actual problem is at the bottom of the post.
=========================================
==============CONFIGURATION==============
=========================================
**These are the *enabled* settings**
Surface Area Configuration
--Local and remote connections
----Using TCP/IP only
SQL Server configuration Manager
--Protocols for MSSQLSERVER
----Shared Memory
----TCP/IP
--Client Protocols
----Shared Memory
----TCP/IP
SSMS
--Server Properties
----Security
------SQL Server and Windows Authentication mode
----Connections
------Allow remote connections to this server
--Login Properties - sa
----Both enforcement options *unchecked*
----Default database - master
----Status
------Permission to connect - Grant
------Login - Enabled
=========================================
===============STARTUP LOG===============
=========================================
2009-09-08 14:29:36.82 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2009-09-08 14:29:36.82 Server (c) 2005 Microsoft Corporation.
2009-09-08 14:29:36.82 Server All rights reserved.
2009-09-08 14:29:36.82 Server Server process ID is 2188.
2009-09-08 14:29:36.82 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-09-08 14:29:36.82 Server This instance of SQL Server last reported using a process ID of 5300 at 9/8/2009 2:29:31 PM (local) 9/8/2009 6:29:31 PM (UTC). This is an informational message only; no user action is required.
2009-09-08 14:29:36.82 Server Registry startup parameters:
2009-09-08 14:29:36.84 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-09-08 14:29:36.84 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-09-08 14:29:36.84 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-09-08 14:29:36.91 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-09-08 14:29:36.91 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-09-08 14:29:38.77 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-09-08 14:29:39.24 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-09-08 14:29:41.29 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-09-08 14:29:41.37 Server Database Mirroring Transport is disabled in the endpoint configuration.
2009-09-08 14:29:41.55 spid5s Starting up database 'master'.
2009-09-08 14:29:42.13 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-09-08 14:29:42.60 spid5s SQL Trace ID 1 was started by login "sa".
2009-09-08 14:29:42.74 spid5s Starting up database 'mssqlsystemresource'.
2009-09-08 14:29:43.58 spid9s Starting up database 'model'.
2009-09-08 14:29:43.60 spid5s Server name is 'TANDEL-47'. This is an informational message only. No user action is required.
2009-09-08 14:29:43.76 Server Error: 17190, Severity: 16, State: 1.
2009-09-08 14:29:43.76 Server FallBack certificate initialization failed with error code: 1.
2009-09-08 14:29:43.80 Server Warning:Encryption is not available, could not find a valid certificate to load.
2009-09-08 14:29:43.83 Server Server is listening on [ 'any' <ipv4> 1433].
2009-09-08 14:29:43.83 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2009-09-08 14:29:43.83 Server Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2009-09-08 14:29:43.83 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2009-09-08 14:29:43.83 Server Dedicated admin connection support was established for listening locally on port 1434.
2009-09-08 14:29:43.83 spid9s Clearing tempdb database.
2009-09-08 14:29:43.91 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-09-08 14:29:44.79 spid13s Starting up database 'msdb'.
2009-09-08 14:29:44.79 spid15s Starting up database 'eVisioning4.3'.
2009-09-08 14:29:44.79 spid14s Starting up database 'ReportServerTempDB'.
2009-09-08 14:29:44.79 spid12s Starting up database 'ReportServer'.
2009-09-08 14:29:47.49 spid9s Starting up database 'tempdb'.
2009-09-08 14:29:49.23 spid12s The Service Broker protocol transport is disabled or not configured.
2009-09-08 14:29:49.24 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-09-08 14:29:50.40 spid12s Service Broker manager has started.
2009-09-08 14:29:51.35 spid15s CHECKDB for database 'eVisioning4.3' finished without errors on 2009-08-09 00:00:08.340 (local time). This is an informational message only; no user action is required.
2009-09-08 14:29:51.43 spid5s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2009-09-08 14:29:51.43 spid5s Recovery is complete. This is an informational message only. No user action is required.
=========================================
==========DESCRIPTION OF PROBLEM=========
=========================================
*Note* all connection attempts are being made inside SSMS.
When connecting through Windows Authentication, I can log in just fine using my domain account. When I attempt to log in through the SQL Server "sa" account, I get the following message:
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.) (Microsoft SQL Server, Error: 233)
This corresponds with the following entry in the log:
2009-09-08 14:33:52.69 Logon Error: 18456, Severity: 14, State: 8.
2009-09-08 14:33:52.69 Logon Login failed for user 'sa'. [CLIENT: <local machine>]
If I specify in the connection dialog to explicitly use TCP/IP, instead of the above message, I simply get the same "login failed" entry as the logfile (minus the State 8 info).
Now, I know that State 8 typically means a password mismatch, however I went in early on in the troubleshooting process and changed the password to the letter 'a' for the purpose of eliminating any possible mistypes. I am 100% certain the password I'm entering is correct.
I can log in via the 'osql' shell command without any problems.
The problem only seems to crop up when using the SSMS app (installed on the same machine as the SQL Server).
Additionally, I tried creating a new user and logging in through it. Same problem as 'sa'.
I've tried just about every reasonable combination of settings I can think of. I don't use SQL Server myself, so I'm running out of ideas on where to go from here.
Thoughts?
--Zack Townsend