TCP Provider: Only one usage of each socket address is normally permitted. ...error after server migration.

Thanks for your comment jimpen.  Connection string shown is just an example of how ours is formatted.

Both my old and new servers run SQL Server 2005 on port 58646 for reasons of security through obscurity.

According to the SQL Server Configuration Manager, SQL Server Browser is stopped, with Start Mode set to Disabled

Ok, this one will probably take some work to troubleshoot. You up for it?

What SP are you on? SSMS --> Help --> About --> Copy info.

Have you run the profier against the server & db(s)?

What are the server specs old to new?

Have you looked at perfmon?

SQL Server 2005 Service Pack 3

Microsoft SQL Server Management Studio      9.00.4035.00
Microsoft Analysis Services Client Tools      2005.090.4035.00
Microsoft Data Access Components (MDAC)6.0.6001.18000 (longhorn_rtm.080118-1840)
Microsoft MSXML                                    3.0 6.0
Microsoft Internet Explorer                        7.0.6001.18000
Microsoft .NET Framework                        2.0.50727.3074
Operating System                                    6.0.6001

I've run perfmon just now, and the profiler against the SQL instance but I'm not seeing anything unusual.  I'm not very experienced using these tools.  Any clues about what to look at?

Server specs old to new (via PC Wizard 2009):

OLD Server

Mainboard :      FUJITSU SIEMENS D2461-C1
Chipset :      nVidia nForce 410
Processor :      AMD Athlon X2 BE 2350 @ 2100 MHz
Physical Memory :      1024 MB
Video Card :      Nvidia Corp GeForce 6150 LE
Network Card :      Nvidia Corp MCP51 Ethernet Controller
Operating System :      Microsoft Windows Server 2003 Professional 5.02.3790 Service Pack 2

NEW Server

Mainboard :      FUJITSU SIEMENS D2461-C1
Chipset :      nVidia nForce 410
Processor :      AMD Athlon 64 @ 2400 MHz
Physical Memory :      2048 MB (2 x 1024 DDR2-SDRAM )
Video Card :      RDPDD Chained DD
Network Card :      Nvidia Corp MCP51 Ethernet Controller
Operating System :      Windows (R) Web Server 2008 Professional 6.00.6001 Service Pack 1

At 2GB you are essentially going to be hitting memory and page swapping on a regular basis.

The recommendation for the Web Server alone is 2GB. SQL Server will try to take 2GB by the default install. Its minimum spec is 512.

As far as what to look at in the perfmon:

Pages/Sec
Avg. Disk Byte/Transfer
Avg. Disk Queue Length
% Processor Time
NIC Throughput
then under the SQL ones
Lock Timouts/Sec            SQLServer:Locks
Lock Requests/Sec         SQLServer:Locks
Deadlocks/Sec                SQLServer:Locks
Buffer Cache hit ratio      SQLServer:Buffer Manager
Page Life expectancy      SQLServer:Buffer Node


Windows Web Server 2008
http://www.iis.net/default.aspx?tabid=27

SQL Server 2005 32-bit System Requirements
http://www.microsoft.com/sqlserver/2005/en/us/system-requirements.aspx

Not much activity on the server this afternoon, so using perfmon is not showing much.  Again the old server didn't have this issue and it had half the system memory to work with.  The database grows very slowly.

Again my problem is the error:
TCP Provider: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Are you telling me that the most likely root cause of thousands of TCP 'connections' in a TIME_WAIT state is that the database is not handleing requests in a timely manner?  Just some context, this error is being logged roughly 15 times a day, I have only encountered it one time, I reloaded the page and everything was fine, otherwise site performance is normal.  I am wondering if database connection pooling is not happening, or why a TCP connection is even necessary since the request and destination are both the local machine at 127.0.0.1

Thanks for reading.

I think this link will explain the issue fully and has a resolution:
---------------------------------------------------------------
Common tips and tricks from a SQL Developer Support perspective
http://blogs.msdn.com/spike/archive/2008/08/26/provider-tcp-provider-error-0-only-one-usage-of-each-socket-address-protocol-network-address-port-is-normally-permitted.aspx
---------------------------------------------------------------

>> or why a TCP connection is even necessary since
>> the request and destination are both the

Technically anything that isn't an SQL Service application uses TCP (or other network protocol) to connect SQL, even if it is on the same box. There really isn't a way around it.

Ok, I changed my connection string (see below) based on your suggestion, but I still have a thousands of TCP connections to the database and database requests are still intermittently failing with the following error message:  TCP Provider: Only one usage of each socket address (protocol/network address/port) is normally permitted.

BEFORE:
Provider=SQLNCLI;Server=127.0.0.1,58646;Database=databasename;Uid=username;Pwd=password;

AFTER:
Provider=SQLNCLI;pooling=true;Persist Security Info=True;Server=127.0.0.1,58646;Database=databasename;Uid=username;Pwd=password;

But I don't think it will make a difference given the page you reference states ' if the application is not a .Net app, instead it uses, for example VBScript, it will not use pooling '  Again this is a Classic ASP application not the newer .NET

Apologies for the delayed response, any ideas?

OK, thank you very much for your efforts jimpen.