December 13, 2012 at 8:28 am
I have a SQL2008 Express server where the only sysadmin is sa and no-one knows the sa password. I am an Admin on the server. I start sqlserver in single user mode from the command line. But when I try to connect via sqlcmd -S instance -E to add my domain login, I get this message:
Named Pipes Provider: Could not open a connection to SQL Server [53].
Sqlcmd: Error: Microsoft SQL Native Client: 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 for SQL Server does not allow remote connections.
Remote connections are enabled. Is this another process, maybe the app, taking the one connection?
Thanks all.
December 13, 2012 at 8:34 am
you could check if there are any connections to your SQL Server by doing a netstat.
netstat -an | find "1433"
If there are any established connections the output will tell you the host that the connection is coming from. This will only show if you app is connecting with TCP.
December 13, 2012 at 8:59 am
Thanks. I'll try that tomorrow. My window for stopping the server today is over.
December 14, 2012 at 8:01 am
The problem was between the chair and the keyboard.
I was valuing the -S parameter wrong in my sqlcmd login attempt.
December 14, 2012 at 8:44 am
As long as you are a local windows admin you can break into SQL via a back door. It requires a SQL service restart and is pretty simple. If you need it get back to me I have it on file somewhere.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply