- Failed to connect to server DESKTOP-68S3Q92. (Microsoft.SqlServer.ConnectionInfo) Additional Information: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
- Login failed for user
- Other errors related to services and connections
There could be a number of reasons for these errors to occur, but in general, ensure you perform the following once you install a new instance of SQL Server:
- NOTE: Password for installation-registered "sa" account is NULL (unless speciffied/changed by user)
- By default, mixed mode authentication is disabled, thus only Windows Authentication is enabled. This means you may not be able to login with SQL Server Authentication after express-installation. To enable mixed mode authentication:
Login with Windows Authentication
Right-Click the SQL Server instance
Select "Properties" =>Security
Select "SQL Server and Windows Authentication mode (see illustration below)
-
Ensure the registered login account is enabled (Under Status page of the account registration page, select ENABLED under Login section)
-
Enable TCP/IP protocl in Sql Srver Configuration Manager.
Open the Sql Server group of services from the Start menu; locate the "Sql Server xxxx Configuration Manager" => Right Click =>Run as Admninistrator
Select "Sql Server Network Configuration" => Protocol for MSSQLSERVER (dbl-click)
Locate "TCP/IP" and select "Enabled"
RESTART THE Sql Server service (OR all 3 services: SQL Server; SQL Server Agent, SQL Server Browser) in the Control Panel Settings of your operating system
Please note: This is NOT from Microsot, but my own experiences as I work with SQL Server. Please comment feedback below.
No comments:
Post a Comment