October 6, 2009 at 9:40 am
When I try to connect to Server through SSMS, I get this error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
It is able to connect to other instances of other servers, fine.
if I try to start it in minimum configuration mode, I get this error:
Your SQL Server installation is either corrupt or has been tampered with (Error getting instance ID from name.).
Any thoughts/help of where the problem is.
Thx
Dan
October 6, 2009 at 9:47 am
Sorry Dan - should have read all the way thru ...Does this help:
http://blogs.msdn.com/john_daskalakis/archive/2008/11/20/9128335.aspx
October 6, 2009 at 9:51 am
is this a default instance or named instance on that server.
October 6, 2009 at 9:51 am
Yes, it could be many reasons for this issue.
If ping is fine, I would try connect by IP and port# instead of name.
October 6, 2009 at 9:53 am
if its a named instance try giving port#
October 6, 2009 at 9:53 am
Seems like a registry issue all right. Please look at this:
October 6, 2009 at 12:15 pm
Thanks for your input.
Registry.. oh no!
named instance; ping does not work(times out)
here is the background.. (I first thought this may not have anything to do with it.. but the more I think.. it may be related..)
http://www.sqlservercentral.com/Forums/Topic797329-361-2.aspx (From post 798099 on)
Thanks much
Dan
October 6, 2009 at 12:22 pm
The second link suggests "re-run sql setup and choose Advanced / registry rebuild". Is this from the CD or command prompt? (http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/a8cc09a9-7500-4fc3-90f4-fd5fff94509b)
I changed the command as in first link, but that gave the same error ( http://blogs.msdn.com/john_daskalakis/archive/2008/11/20/9128335.aspx )
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply