• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 412
  • Last Modified:

SQL Server Error

Never seen this before. Turned on my computer and tried to connect to my local machine with Management Studio. Tried rebooting, nothing. Here's the error:

a connection was successfully established with the server, but then an error occurred during the login process. (provider: shared memory prrovider, error 0 - no process is on the other end of the pipe) (microsoft sql server, error: 233).

Please help!

  • 3
1 Solution
This error usually indicates that the server closed the connection, e.g. during login verification.

The best is to check for any messages from SQL Server correlated to the time of the failure - either in the Application EventLog or in the ERRORLOG file (by default located in the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory).  There is a chance they provide more information to identify the root cause of the failure.
infotechelgAuthor Commented:
the log file hasn't been updated since 8/16
infotechelgAuthor Commented:
I take that back. The log file wasn't in the MSSQL.1 folder, it was in the MSSQL.3 folder.

Is this the issue?

2010-08-31 09:41:05.04 Logon       Could not connect because the maximum number of '1' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT: <local machine>]
2010-08-31 09:41:05.04 Logon       Error: 17809, Severity: 20, State: 3.
infotechelgAuthor Commented:
Something about the VIA protocol not being enabled? I have no idea what that means, but that was the issue.
Ryan McCauleyData and Analytics ManagerCommented:
Is the SQL Server running locally? Does the login failure happen almost immediately, or does it take about 30 seconds to timeout?

 - If it's immediate, then SQL Server is denying your login request, which indicates that it's not configured properly.
 - However, if it times out, then I'd suspect the SQL Server service is stopped - check your Administrative Tools -> "Services" list to see if "SQL Server" is running, and start it if it's stopped for some reason.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now