1.1 to 2.0 migration now requires TCP/IP port in ConnStr

G

Guest

Just migrated an ASP.NET 1.1 application to ASP.NET 2.0 and could no longer
connect to SQL Server 2000. It uses TCP/IP with a non default Port Number.

The problem is fixed by adding the TCP/IP port to the connection string like
so:

... server=mySqlServer2000,4444; uid=sqlUser; pwd=****...

Why did this work without the TCP/IP port number on ASP.NET 1.1 and not
ASP.NET 2.0??

TIA
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Migration from 1.1 to 2.0. 2
Failing to connect to remote SQL Server 2000 from ASP.NET 2.0 application 0
ASP.NET 2.0/SQL Server 2000 Connection Problem. 1
Event ID 1078 (State Server has closed an expired TCP/IP connection...) 0
Migration from .Net 1.1 to .Net 2.0 couldn't load assembly or file 0
TCP/IP port exhaustion - Unable to connect to the remote server 3
Switching a Dataprobe iP-415/815 (basic) using TCP 0
Using .NET 2.0/3.0 component in ASP.NET 1.1 6

Members online

Total: 31 (members: 1, guests: 30)
Robots: 379

Forum statistics

Threads
473,755
Messages
2,569,536
Members
45,014
Latest member
BiancaFix3

Latest Threads

Top