[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

SQL Server 2008R2 Connection Problem

Posted on 2011-02-11
6
Medium Priority
?
1,433 Views
Last Modified: 2012-05-11
I have a Windows 2008R2 Server in my home, and have installed SQL Server 2008R2 on it.  I am having connection problems, both locally and on the server, connecting to this SQL Server instance.

Scenario 1 - Was getting error 233 when attempting to connect using SSMS on the server (localhost).  I thought I had this problem solved last night, after finding suggestions to disable shared memory protocol, as well as named pipes.  I went through several trial and error attempts, and after finding a suggestion to connect to the master db instead of <default>, it worked.  After that, connecting to <default> worked.  I then turned Named Pipes and Shared Memory back on, and it still worked.  

Scenario 2 - Now that I got it connected locally, I went to my laptop.  After much frustration, I found that Windows Firewall was blocking me, and I put the exception in, and was able to connect with SSMS using the remote client.  Good.

This morning, on the laptop, I connected using SSMS, no problem.  Then I started to do an import from a flat file.  When I got to Finish, I clicked it, and I got a login error (don't remember what error it was now, but it suggested too many connections, server too busy - you know - the ever-so-helpful Microsoft errors).  I disconnected from the server in SSMS, and now I cannot connect again.  Nothing has changed on the server.  I get the 10054 error, with the statement  that a connection was established, but there was a problem during the login process, and that the connection was forcibly closed.

I went back to the server, logged in, and using SSMS on localhost, I end up getting the 233 error.  I turned off shared memory, and connected to master instead of <default>, and that worked.  Then I connected to <default> and that worked.  I turned shared memory back on, and it still worked.  But the remote SSMS from the laptop still won't connect.

Also, TCP/IP and Named Pipes are both turned on, and remote connections are allowed.  I'm puzzled at the inconsistency of this problem.  Any suggestions?
0
Comment
Question by:hopmedic
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
6 Comments
 
LVL 2

Author Comment

by:hopmedic
ID: 34871202
Ugh... Now it's giving me the 10054 error when I try to connect from the server (localhost)...
0
 
LVL 2

Author Comment

by:hopmedic
ID: 34871551
Grrr... I got it to working again, by disabling shared memory and named pipes.  I'd still like to know why it doesn't work with them enabled.  I don't recall reading anywhere that only one protocol is allowed...  :/
0
 
LVL 2

Author Comment

by:hopmedic
ID: 34871672
Ok - I stepped away from the laptop, and then came back to import the flat file, and I got a prelogin error.  Now I can't connect at all from the laptop.  I went back to the server, and from localhost, I got the 10054 error.  Instead of localhost, I tried (local), and I got a 10053 error (that's a new one for me).  I restart the sql server service, and we're good again.  So since with each change I made before, I had to restart the service, I'm wondering now if restarting the service is what is solving the issue for the moment, and not the changes I've made.  Assuming for the moment that is the case, what is making my sql server service fall asleep?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 2

Accepted Solution

by:
hopmedic earned 0 total points
ID: 34873994
Ok...  I changed the query timeout to zero instead of 600 seconds.  So far it has been working correctly for several hours.  I'm still puzzled what a timeout of 10 minutes would have to do with the login being blocked.  :/
0
 
LVL 52

Expert Comment

by:Vitor Montalvão
ID: 34887152
hopmedic, what's the SQL Server version and edition?
0
 
LVL 2

Author Closing Comment

by:hopmedic
ID: 34932058
Because no other solution was offered, and the problem was resolved.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question