Re: Access 2007->SQL Server2005 "connection was forcibly closed",G

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi William,

thanks for your hint, I already found your blog post when researching for
the problem and checked this on both servers, unfortunately the maximum
connections setting is 0 in both cases so I cannot reach anything with
flowers and candy...:-)
Moreover I tested this in another environment with Access 2003 and SQL 2005
Server with AdventureWorks: If I cut the maximum number of connections to for
example 20 connections and try to open more than 20 tables with Access the
SQL Server simply blocks any further try to open another table until I close
one. So this cannot be the reason for the cutting of the connection. What
happens here is that I CAN open all the tables of the database, no problem.
As written before to Erland the tool TCPView from Sysinternals shows that all
connections are made, some with "TCP_WAIT". But I can see the contents of all
opened tables in Access. Then by simply waiting some minutes I can see with
this tool that the connections are cutted one by one, first the "TCP_WAIT"
and then the "ESTABLISHED" ones. And if this happens, the error occurs on
Access. So there must be some software component which cuts the connections
actively. This doesn't happen with the SQL Server 2000 but with SQL Server
2005. If it is not any setting on the SQL Server it must be in Windows - or,
what I cannot exclude at the moment, with some VMWare driver or cluster
problem because as far as I know the SQL Server 2005 is running on VMWare ESX
server with a Windows cluster.

Cheers,

Christian

"William Vaughn (MVP)" wrote:

Google "Forcibly closed Vaughn" and on my blog you'll find a solution to
your problem--at least I expect it is.

http://betav.com/blog/billva/2008/11/solution-forcibly-closed-sql-s.html


hth

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________



"Erland Sommarskog" <esquel@xxxxxxxxxxxxx> wrote in message
news:Xns9C6EF023433A3Yazorman@xxxxxxxxxxxx
Christian Coppes (ChristianCoppes@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
And I saw comparing the trace of TCPView above that SQL Server 2005
always
connects to port "2594" and SQL Server 2000 to port "ms-sql-s". Does this
mean that 2005 is using TCP and 2000 is using named pipes?

No, I think ms-sql-s means that SQL 2000 is using port 1433, which is
the default port for the default instance. That is, ms-sql-s is a
registered name for port 1433. In the same vein, I guess that TCPVIEW
does not present port 25 as 25, but as "smtp". (I don't have TCPVIEW
here, but I would not be surprised if there is an option to change
this.)

Are SQL 2000 and SQL 2005 running on the same Windows box, or on
different ones? If they are on different, there could be Windows
differences. If they are on the same box, it's getting a little more
intriguing.

In any case, since SQL 2005 runs on port 2594, this indicates that it's
a named instance. This means that there is one more player in the
game, the SQL Server Browser service. To be able to connect the name
instance, the client first connects to the Browser Service on UDP port
1434, to get the port number for the instance.

If you change the connection string to read server,2594 rather than
server\instance, you will not make the connection on port 1434. Not that
I see that it has anything to do with it, but it is worth trying.




--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

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


.

Relevant Pages

  • Re: SQL2005: Cannot connect error 11001
    ... The famous Windows Firewall (turned on my Server from which I'm trying to ... Exception Details: System.Data.SqlClient.SqlException: Login failed for user ... Try starting the SQL Server ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • Re: network programming: how does s.accept() work?
    ... The program you contact at Google is a server. ... so, the server will usually assign a new port, say 56399, specifically ... connections to a server remain on the same port, ... sockets is what identifies them. ...
    (comp.lang.python)
  • Nimda.E/unknown memory resident, internet-aware processes
    ... a client's NT 4.0 server was infected with what appeared to be ... network traffic and saw several suspect connections. ... one other connection to port 2787. ... along with about 500 other compromised systems on just that one IRC server. ...
    (Incidents)
  • Re: VB app connect THROUGH proxy to a remote SQL database
    ... The whole "HTTP proxy is way more secure than allowing outgoing ... the client app and the SQL server are on ... incoming connections to the SQL server are not the problem - it's ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Failed connections to remote 2k SQL Server
    ... It could be a port issue - that would be my first guess. ... you need to open up UDP 1434 for SQL Server name ... TCP Ports Needed for Communication to SQL Server ... >server's network utility, and client network utility, and ensured that they ...
    (microsoft.public.sqlserver.setup)