June 20, 2015 at 10:55 pm
hello
i use sql server 2012 in windows server 2008
it was worked well
but one day when i want to connect to sql server i faced an error
i set the user name and pass correctly but i cant log in at all!
an error icon is on my intance
unfortunately i don't have backup :angry:
error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Error connecting to 'WIN-4K'.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to 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%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
------------------------------
The system cannot find the file specified
------------------------------
BUTTONS:
OK
------------------------------
is any way to repair it ? if not how can i get database backup ?
please Help me
Thank you
June 21, 2015 at 2:32 pm
That basically means it can't see the SQL Server. Can you ping the server?
Is the SQL Server service running on the WIN-4K server? To check this, log in to the server, and click Start > Run, type "services.msc" and press "OK", search for "SQL Server", double-click on it; what does it say beside "Service status:"? If it doesn't say "Running", click "Start".
June 21, 2015 at 10:33 pm
thanks
i checked the status of sqlserver in Windows services,but it was null! right click and select start but i gotan error!
error:
and i checked instanse server in Configuration Manager, it was stoped and when i start it i faced This error :
why it cant't start?!
how can i repair this?
June 22, 2015 at 5:22 am
June 22, 2015 at 1:47 pm
First I would check the Application log to see if it has any entries of value as to why SQL Server would not start. If that does not lead to anything try looking in the directory where the SQL Server Error logs are located and open up the ERRORLOG file in a text editor and see what it has.
Anything change recently?
Joie Andrew
"Since 1982"
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply