|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Troubles connecting with VMWare?getting strange, sparatic connectivity issues when we execute commands. Here's a short list of errors: - 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 - A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) - A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) - A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine.) They are sparadic (we'll have hundreds of successful commands then suddenly one of these) and if we rerun the exact same statement, it works properly. The only commonality with the errors is "provider: TCP Provider, error: 0". So we've added an awkward work-around that if the error message contains that text, rerun the Command.Execute. That work around effectively fixes our product, but it feels like such a kluge that I wanted to see if there was a proper fix? -BKN Bryce,
Check out the following Microsoft KB article Error message when you try to connect to an instance of SQL Server 2005: "No process is on the other end of the pipe" or "An existing connection was forcibly closed by the remote host" http://support.microsoft.com/?kbid=919710 Show quote "Bryce K. Nielsen" <br***@sysonyx.com> wrote in message news:ulzrm18lGHA.4712@TK2MSFTNGP04.phx.gbl... > Anyone use ADO.NET 2.0 connecting to a SQLServer through VMWare? We're > getting strange, sparatic connectivity issues when we execute commands. > Here's a short list of errors: > > - 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 > - A connection was successfully established with the server, but then an > error occurred during the login process. (provider: TCP Provider, error: 0 - > An existing connection was forcibly closed by the remote host.) > - A transport-level error has occurred when receiving results from the > server. (provider: TCP Provider, error: 0 - An existing connection was > forcibly closed by the remote host.) > - A transport-level error has occurred when receiving results from the > server. (provider: TCP Provider, error: 0 - An established connection was > aborted by the software in your host machine.) > > They are sparadic (we'll have hundreds of successful commands then suddenly > one of these) and if we rerun the exact same statement, it works properly. > The only commonality with the errors is "provider: TCP Provider, error: 0". > So we've added an awkward work-around that if the error message contains > that text, rerun the Command.Execute. That work around effectively fixes our > product, but it feels like such a kluge that I wanted to see if there was a > proper fix? > > -BKN > > > Check out the following Microsoft KB article Thanks, but I don't think it's relavent. We're not using SSL and the problem > > Error message when you try to connect to an instance of SQL Server 2005: > "No process is on the other end of the pipe" or "An existing connection > was forcibly closed by the remote host" > http://support.microsoft.com/?kbid=919710 > > rarely occurs, not every time. It's very sparadic and if we immediately re-execute the SQL statement, it works fine (see my work-around, it immediately resends the command if we get this error, and it never happens 2x in a row). -BKN Just a suggestion, Have you tried to set the network to NAT instead of
Bridged in the VMware settings menu? Show quote "Bryce K. Nielsen" <br***@sysonyx.com> wrote in message news:e36%23PuSmGHA.4436@TK2MSFTNGP05.phx.gbl... >> Check out the following Microsoft KB article >> >> Error message when you try to connect to an instance of SQL Server 2005: >> "No process is on the other end of the pipe" or "An existing connection >> was forcibly closed by the remote host" >> http://support.microsoft.com/?kbid=919710 >> >> > > Thanks, but I don't think it's relavent. We're not using SSL and the > problem rarely occurs, not every time. It's very sparadic and if we > immediately re-execute the SQL statement, it works fine (see my > work-around, it immediately resends the command if we get this error, and > it never happens 2x in a row). > > -BKN >  |
|||||||||||||||||||||||
Other interesting topics