April 24, 2014 at 9:06 am
I Am Using a Windows 7 operating system with SQL SERVER 2012 , trying to restore the master database.
I have put the instance in Single user mode by including -m in the startup parameters.
I have stopped the instance using NET STOP
When I Start using SQLCMD -s <Computername\instance name> -E
it Shows up Error=
Named pipes Provider could not open a connection to SQL Server [2]..
SQLCMD Error MS SQL SERVER : Login Timeout expired
SQLCMD Error MS SQL SERVER : A network related or instance -specific error has occured while establishing a connection to SQL SERVER. SERVER is not found or Not Accessible .Check if instance is correct and if SQL SERVER is configured to allow remote connections.
Please Help me with Query.
Thanks
Sanjeev
April 24, 2014 at 9:21 am
Have you navigated to the right folder before running sqlcmd? I just tested it in the wrong location and got that error message.
April 24, 2014 at 9:31 am
Run Nat start in cmd and check if the instance you are connecting to is there.
😎
April 24, 2014 at 6:10 pm
Haven't done any such step? If you can be more elobrative would be of much needed help.
Thanks
April 24, 2014 at 6:11 pm
I have ran Net start and Stop i Runs fine on the instance
April 24, 2014 at 10:14 pm
allamsanjeev (4/24/2014)
Haven't done any such step? If you can be more elobrative would be of much needed help.Thanks
Open up command prompt (cmd.exe)
type: net start
and hit enter
the output should be:
These Windows services are started:
....
SQL Full-text Filter Daemon Launcher (SQL2012)
SQL Server (SQL2012)
SQL Server Analysis Services (SQL2012)
SQL Server Browser
SQL Server Integration Services 11.0
SQL Server VSS Writer
where the instance name is in parentheses, this case SQL2012, check what the instance name is in your case.
😎
April 25, 2014 at 11:39 am
I did try that, still the problem persists, looks like it is OS permissions issue..
April 25, 2014 at 12:16 pm
there's not multiple instances, right?
you know you used lower case -s and not uppercase -S? and the parameter flags are case sensitive
based on what you posted, this should be working
SQLCMD -S .\SQL2012 -E
Lowell
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply