Hello ...
Using Ent. Library Jan. 2006 release and .Net Framework 2.0, I'm connecting to SQL Server 2000 using Microsoft.Practices.EnterpriseLibrary.Data.Sql.
I have a windows service that processes jobs asynchronously and from time to time, I'm getting the following error --
"A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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. (TCP Provider error: 0 - An existing connection was forcibly closed by the remote host. "
What's surprising is the error message saying SQL Server 2005. Has anyone encountered and resolved this?
Thanks.
allanroy
I guess you installed the SNAC on your system, right ? Thats where the message comes from.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
What is SNAC?
Thanks.
allan
|||Nothing to eat ;-) It s the SQL Native Client.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
The SQL Native Client is installed in my client machine and not on the server that host the SQL Server 2000 and my windows services. Ones a job is requested from a client machine, the process is asynchronous and processing happens only on the server.
allan
|||Are you using connection pooling, if yes it could be that the connection used is not released from the pool, leading to the error message, that the server cannot be contacted.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
No comments:
Post a Comment