462 error

We have an application that connects to a MS SQL database.
Occasionally we get this message.
"Error: 462: The remote server machine does not exist or is
unavailable"
Any thoughts as to what would be causing this?You did not provide any info about your SQL Server' s Edition and version.
Ensure your SQL Server services are running. You can check them using SQL
Server Configuration Manager.
In SQL Server 2005 Express or Developer Edition, Remote Connections will be
disabled by default. Go to Surface Area Configuration tool to enable it.
If you have not, configure TCP\IP or NP protocol from SQL Server
Configuration Manager.
Also, can you post your connection string?
--
Ekrem Önsoy
"MikeS" <mike.sheats@.gmail.com> wrote in message
news:1193231306.041192.37630@.i13g2000prf.googlegroups.com...
> We have an application that connects to a MS SQL database.
> Occasionally we get this message.
> "Error: 462: The remote server machine does not exist or is
> unavailable"
> Any thoughts as to what would be causing this?
>|||I have seen this error, but its been a while. As I recall, the problem was
in DNS.
In SQL Server (2008, 2005, 2000, 7, 6.5, etc, etc, etc ... and Windows XP,
2000, 2003, etc, etc, etc ...) you access a remote server by hostname. What
this means is that you're dependent on the network DNS service (or possibly
your local hosts file) to provide you with the IP address you actually need
to connect.
While I dislike making connections via IP address, if you change your app to
use the IP and the problem goes away, it will confirm that the problem is
DNS.
Good luck,
Jay
PS. It is generally better to specify DB Server & OS versions. It's at your
fingertips and you never know when it will be relevant. Of course, I forget
sometimes too :)
"MikeS" <mike.sheats@.gmail.com> wrote in message
news:1193231306.041192.37630@.i13g2000prf.googlegroups.com...
> We have an application that connects to a MS SQL database.
> Occasionally we get this message.
> "Error: 462: The remote server machine does not exist or is
> unavailable"
> Any thoughts as to what would be causing this?
>