I have a VB6-application that opens a ADO connection to a sql server database at startup. Everything is ok, as long as there is not much database work to do. As soon as I start a calculation that works a lot in the database (reads and writes in appr. 10 tables), it takes about 1 minute and I get the message: SQL Server does not exist or acess denied. Since the app shows the status of the job you can see that the error occurs always after exactly the same number of database operations done. the strange thing is, that the error shows up on XP prof. only. The same app doing the same job on the same database works fine in W2K. What I've tried so far: - installed all available service packs and hotfixes on XP maschine - updated existing MDAC 2.71 to 2.8 - changed connection string to use OLEDB instead of DSN - deaktivated pooling The error does NOT occur when working with MSDE, no matter wether local or remote installation.
I solved the problem creating these entries in the registry: path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\Tcpip\Parameters type: DWORD name: TcpTimedWaitDelay value: 30 (decimal)
We were also having this same exact problem after we changed one of our 2 web servers over from Windows 2000 to Windows 2003. We looked and looked and found tons of people having the same problems, none of which had answers. We were THRILLED when we finally found this thread. It was honestly the first time somebody had the same problem we did and where somebody else had solved it.
We created these two registry keys on our Windows 2003 server and everything has been working great ever since. Actually, it's been working better than the 2000 machine is. There are less errors and the site seems to run faster. I know IIS6 is faster, but we can tell that it's running a little better.
What we did was tweak the numbers here a bit to use 15 for the TcpTimedWaitDelay and 40000 for the MaxUserPort. We found that these numbers worked better for us.
Anyway, I just wanted to post in case somebody else that's having this super annoying and frustrating problem comes across this message. There is hope and there is a fix.
The craziest thing of all, which still drives me nuts, is the fact that nobody knows why it happens. Oh well, as long as it's working I'm happy!
> We were also having this same exact problem after we changed one of our > 2 web servers over from Windows 2000 to Windows 2003. We looked and > looked and found tons of people having the same problems, none of which > had answers. We were THRILLED when we finally found **this thread**. It ...
Hi Don,
What is **this thread**? What thread are you referring to? Your answer begins as new thread in my OE news reader, and I'd be THRILLED to know where you found that "does not exist" solution.
There is no one solution for the error - it depends on a lot of different things. If you have pooling disabled, you can reference the articles Don referred to for changes in the registry: TCP/IP Settings for SQL Server Drivers When Pooling Is Disabled http://support.microsoft.com/?id=328476 PRB: "WSAEADDRESSINUSE" Error Message When You Try to Connect Through an Anonymous Port After You Increase the IMAP Connection Limit http://support.microsoft.com/?id=319502
-Sue
On Fri, 28 Jan 2005 09:28:40 +0100, "Frank Lehmann"
>"Don Kitchen" <donkitc...@gmail.com> wrote in message: >news:1106860589.817854.145070@z14g2000cwz.googlegroups.com... >> We were also having this same exact problem after we changed one of our >> 2 web servers over from Windows 2000 to Windows 2003. We looked and >> looked and found tons of people having the same problems, none of which >> had answers. We were THRILLED when we finally found **this thread**. It ...
>Hi Don,
>What is **this thread**? What thread are you referring to? >Your answer begins as new thread in my OE news reader, and I'd be THRILLED >to know where you found that "does not exist" solution.
Thank you both, Sue and Don, for your answers. The registry settings MaxUserPort and TcpTimedWaitDelay are the perfect solution for my problem. I've read somewhere that this behavior of lots of TCP connections not being reused came into Windows out of security reasons in order to prevent that hackers gain access to a server through such an open channel without authentification.
