site not communicating with database
jack_hilary
I have a website on remote server developed using asp.net. I am using MS SQL
2005. My question is that the remote site was communicating with database
well for few days ago but suddenly it stopped communicating with database and
shows me msg. like Server was not found. However I know that there is
database up and running because I can login into it using management studio
and also from my local site on my system by changing connection string I may
communicate with database. But the problem is with remote site, it has
stopped communicating with database suddenly. One strange thing is that I do
not receive any email for this error as I have set application for sending
msg. on any error.
Please kindly have a look on it and tell me what could be the reason that
site is not communicating with database.
Thank you.
Rick Byham, MSFT
request out on the network and didn't get a response. So there are many
possible reasons. If the SQL Server and the client configurations didn't
change, then it was probably the network.
Are you using TCP/IP? Then try to ping the IP address from the client to the
server.
If that works, can you ping the client by name? If not perhaps the TCP/IP
address changed. Try ipconfig /flushdns on the client to refresh the name
resolution.
If you can ping by server name, then start checking the firewalls. Is the
SQL Server a default instance listening on TCP port 1433, and is that port
open? If the SQL Server is not listening on TCP port 1433, the SQL Server
error log will give report the TCP port that SQL Server is using. So you can
open that port.
Can you connect by using the ipaddress,port# as in 123.123.123.123,1500 ? If
you can connect by specifying the port number and if SQL Server is a named
instance or is not listening on the default port, then you need UDP port
1434 to be open for the SQL Server Browser Service. The Browser Service
provides the port number to the client.
Hope this helps.
--
Rick Byham, MSFT
(Implies no warranty or rights)
"jack_hilary" <u59628@uwe> wrote in message news:a722e9a7e77f8@uwe...
jack_hilary via SQLMonster.com
As I have not done such thing (like pinging etc, and also TCP/IP checking)
please support me regarding this.May be this time the problem may get solved
as you have got the root of error.
So please help me regarding this, the solution is one step far only.
Thank you.
--
Jack
Message posted via http://www.sqlmonster.com
Erland Sommarskog
> Hello, Thank you for your reply.
> As I have not done such thing (like pinging etc, and also TCP/IP
> checking) please support me regarding this.May be this time the problem
> may get solved as you have got the root of error.
> So please help me regarding this, the solution is one step far only.
Diagnosing connectivity errors can be difficult, not the least over a
distance. And then I mean the distance between the audience in this
newsgroup and your servers.
Ping is a command you can run from a command-line window. The command
sends small packets to the other computer, which then may report back.
For instance, I do:
C:\ping msnews.microsoft.com
Pinging msnews.microsoft.com [207.46.248.16] with 32 bytes of data:
Request timed out.
Request timed out.
This output tells us two things: msnews.microsoft.com is a known
name - as we see the IP-address. We are not able to reach the computer -
or it prefers not to respond to PING. (The latter happens to be true
in this case, but the default is for machines to respond to PING.)
Anyway, the reason for the dropped connection has little do with
SQL Server per se, it is likely to be a problem with your network, so
this newsgroup is probably not the best venue for your problem. Hope
fully there are some networking people at the sites you work with
that can help you.
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
jack_hilary via SQLMonster.com
When I pinged then I got the IP Address but it also reported Request timed
out. So please tell me in this case what should I do.
I know you suggested to talk to host company's tech. staff but I think they
are not getting or enable to resolve it.
Erland Sommarskog
> When I pinged then I got the IP Address but it also reported Request timed
> out. So please tell me in this case what should I do.
Put the network cable in.
Seriously, there are so many things that could be the reason. Bad cables,
bad network hubs, incorrect network configurations.
> I know you suggested to talk to host company's tech. staff but I think
> they are not getting or enable to resolve it.
You are pretty hosed then. If your local staff are not able to resolve
the issue, certainly no one on the Internet who nothing about the network
configuration will be able to resolve it either.
--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
jacl_hilary via SQLMonster.com
--
Jack
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-connectivity/201004/1