July 31, 2008 at 9:10 am
Hi,
We, in our application face an issue(not everytime, but sporadically) when one of our web services tries to contact the database to get the results. The error message that we get is as follows.
" An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
The TCP/IP and the Named Pipes are enabled. Also the Local and the Remote Connections are also selected.
What bothers us is that this is not occurring every time but at irregular intervals.
Can anybody help us in this regard.
Thanks,
Sudarsan
July 31, 2008 at 9:49 am
what do your event logs from the machine experiencing the error show? also, what's your environment like? are you using citrix? how are your clients connecting? when exactly is this happened? are your users being prompted to log in?
July 31, 2008 at 11:46 am
We have a web service set up in a machine(database server) and no citrix is used. there are no entries in Event logs also. when the web service tries to make a contact with the database, this error is thrown...
July 31, 2008 at 12:11 pm
That's the generic "cannot connect" message. Ignore all of the extra wording, it just means that when the connection attempt was made, the server could not be contacted.
Since it is an intermittent problem, I would first suspect an inability to connect to the IP or port on your SQL Server. You may want to try a different protocol. If your connection is using TCP/IP, switch the connection to named pipes. Also, verify you are not having a network issue. It could be something as simple as a bad NIC cable, or it could be something complicated in routing on your network. You may want to try running the web service locally on the SQL Server to determine if you are hainv networking issues.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply