all groups > sql server connect > september 2004 >
You're in the

sql server connect

group:

SQL Connectivity failure-lack of knowledge


SQL Connectivity failure-lack of knowledge paul gardiner
9/28/2004 11:15:58 AM
sql server connect:
Brand new W2K3 server in a workgroup, no domain. Server
name and IP address are pingable.
Installed SQL Server 2000 with SP3a, no errors. Chose
Windows authentication. SQL Server service and Agent
service are running, Enterprise Manager on the server
appears fine. No database created yet, trying to connect
to the Northwind db.

Don't know how to make a connection to the Northwind db.
Do I have to create a share for the drive and/or folder
that SQL is on? Do I have to adjust Local security on the
server? On the server, when I try to add
workgroup\computername to Allow Logon Locally, I can
select it, but when I save, I get a message that says "an
extended error has occurred. Failed to save Local Policy
Database." Do I have to create a group on the server and
within SQL that has all the necessary users?

On a workstation,creating and testing an ODBC connection
results in:

Microsoft SQL Server ODBC Driver Version 03.85.1025

Running connectivity tests...

Attempting connection
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.

TESTS FAILED!

I'm obviously missing something. Any help would be
RE: SQL Connectivity failure-lack of knowledge BLiTZWiNG
9/29/2004 4:35:09 PM
Well it would be nice to see your connection string, and to know whether
you're using ASP, ASP.NET or a proper application. But for starters, because
you chose Windows Auth, you need to add a user associated with a windows
security account to the database. open the enterprise manager, go to the
northwind database \ users and add a new user and tick all the roles. If it's
..NET, you need to do this for the NETWORKSERVICE account too (ASPNET on
anything but 2k3).

[quoted text, click to view]
AddThis Social Bookmark Button