December 3, 2012 at 6:54 am
Hi All,
While connecting to database am getting below error.
"A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host."
actually i restarted the system and then again i replced existing log file with the same name. But am not abel to connect to that data base.
so i replced with the old logfile with same name.
After that am getting above error.
Please provide solution for this.
Tahnks,
Ravi@sql
December 3, 2012 at 7:12 am
I guess it is because you restarted SQL Server and trying to connect to the instance from an already opened SSMS Query window.
Try this:
Right-click on query window
Goto Connections
Click on Connect and connect to the instance again.
If this doesn't solve your issue, tell us how you are trying to connect to the instance?
Regards..
December 3, 2012 at 9:36 pm
no actually i closed sql server and opened am able to see other databases except which i wanted to connect.
December 3, 2012 at 10:18 pm
ravi@sql (12/3/2012)
no actually i closed sql server and opened am able to see other databases except which i wanted to connect.
check your SQL server error logs
-----------------------------------------------------------------------------
संकेत कोकणे
December 3, 2012 at 10:22 pm
have you gone thru this link
http://blogs.msdn.com/b/spike/archive/2009/04/16/a-transport-level-error-has-occurred-when-sending-the-request-to-the-server-provider-tcp-provider-error-0-an-existing-connection-was-forcibly-closed-by-the-remote-host.aspx%5B/url%5D
You could also check if the servvice startup type is manual , most probably after the restart the service didnt come back up.
December 4, 2012 at 12:25 am
this connectivity issue due to network failure.please check it using cmd ping -t with IP of server
another possible reason is when service get restart .check using sql query when was last sql server restart
select name .create_date from sys.databases where name='tempdb'
December 4, 2012 at 2:24 am
hemant.raibole (12/4/2012)
this connectivity issue due to network failure
this cant be the case as OP posted above that he is abble to connect with other databases.
This might be bacause wrong reference of that particular database log's file check the refernce is sys.databases.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
December 4, 2012 at 2:34 am
yes you are right if i guess right ... but one senior guy telling that mdf and log files are corrupted now resore it from any other back only the option.they try to detach and attach the but it didnt worked.
any solution for this ?
December 4, 2012 at 2:44 am
ravi@sql (12/3/2012)
no actually i closed sql server and opened am able to see other databases except which i wanted to connect.
Hello Ravi,
Are you able to connect to the database now? Do you see the database at all in SSMS? If yes, is it online or, you are seeing it is suspect mode?
If you are not seeing the database at all, you need to attach it. Right click on databases and click on attach. Then, browse to the physical location of MDF file for the database.
December 4, 2012 at 2:45 am
Bhuvnesh (12/4/2012)
hemant.raibole (12/4/2012)
this connectivity issue due to network failurethis cant be the case as OP posted above that he is abble to connect with other databases.
This might be bacause wrong reference of that particular database log's file check the refernce is sys.databases.
try to set database offline then only try to detach mdf files NOT ldf (if you can afford)
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
December 5, 2012 at 3:42 am
please check database mdf and ldf located disk present or not this might reason .
i already face this error such error .it is showing database online in ssms .
bcoz it is showing entry of database from system catalog..
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply