SQL Server 2000General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
I've recently moved web servers. My previous web server was running sql server 2000. I have installed SQL server 2000 on the new one and have migrated all the databases across to the new one. They are mostly back ends to database driven sites and are working fine.
However, when I try to connect to the new SQL Server via QA it does not allow me in. It gives me the error:
Unable to connect to server
Server: Message17, Level16, State 1
Microsoft ODBC SQL Server Driver DBNETLIB SQL Server does not exist or access denied.
I am also connecting to some of my databases via SQLOLEDB and when I give the Data Source as the ip of the new SQL Server it won't allow it to connect either.
Can anyone point me in the right direction? Have I missed something when I installed it?
Did your old server support "mixed mode authentication", allowing both SQL Server authentication and Windows authentication?
if you do a clean install of SQL Server, by default it only allows Windows authentication.
If this is the issue, you can either change the supported authentication mechanisms in SQL Server, or change the way you connect to the server (recommended).
Everyone is unique, except for me.
While typing this post, I was listening to: If You Have A Cross To Bear You May As Well Use It As A Crutch by Moloko (Track 16 from the album: Things To Make And Do) What's This?
Open the Enterprise Manager, locate your server and right-click it. Choose Properties and then open the Security tab.
There you can switch to Mixed Mode. After the switch, you can log in by supplying SQL Server credentials, like the SA or other SQL accounts.
However, it's often better to use Integrated Security. With IS, you don't supply a user name and password in a connection string, but you connect to SQL Server in the context of the "current user". What user that is, depends. It can be IUSR_MachineName for anonymous html / ASP web sites, or the ASPNET or Network Service account. It can also be the currently logged on user.
Sadly I haven't managed to make it work - however in the log files I noticed this:
'You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
MSDE, or both have been disabled. To enable these ports, you must install
a patch, or the most recent service pack for Microsoft SQL Server 2000 or
MSDE from http://www.microsoft.com/sql/downloads/default.asp'
I've installed the patches but am not sure how to enable the tcp/ip and udp ports again?