Access the answers to your technology questions today.
Subscribe Now
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
Subscribe Now
30-day free trial. Register in 60 seconds.
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Join the Community
by: makerpPosted on 2002-11-29 at 04:21:30ID: 7511419
the problem is with the server not any clients. it looks as though sql server can not creating a listening socket on 1433, this could be becuase another application has claimed this port.
do
netstat /a
at the command line to see is anything is on that port.
you can try changing the port sql server listens on and change the port your clients use (do this in odbc manager). see books online for this