sql server connect: First, may I say that I truly appreciate the time people spend on
these forums to help others out; it's a wonderful community.
Second, I'm afraid that my problem has been answered many times in the
plethora of material I've researched and referenced trying to solve my
particular problem. However, I've tried so many different suggestions
and made so many adjustments that now I'm thoroughly confused with the
details.

I have a domain which consists of a Windows 2000 Pro OS machine and a
Windows Server 2003 OS machine upon which resides a SQL Server 2000
instance. On the W2KPro machine I have Visual Studio .NET 2003,
within which I've created an ASP.NET webapp (call it WEBAPP) to
communicate with a database on the SQL Server (call it DB). WEBAPP
has been tested on other platforms and works fine. From VS.NET, I can
read everything on DB through the connection functionality provided by
Server Explorer. However, when I run WEBAPP, which has code to
communicate with DB, I continually get error messages, ranging from
'SQL Server does not exist, or access denied' to 'login failed for
user 'xxxxx'. Reason: Not associated with a trusted SQL Server
connection'.

The variations in error messages occur as a result of trying all the
different logins, connections, permissions, etc. that I've used
following each attempt to establish the connection. The following
connection string is typical, in VB:

"Data Source=<SERVERNAME>,1433;" & _
"Initial Catalog=DB;" & _
"User ID=frefacad; Password=aspnettest;"

Is there a connect the dots process which I could follow to clear up
the confusion and finally establish the connection? Please don't
tell me to see anything that has been posted so far. I'm fairly
certain I've searched everything, but can't identify a situation that
pertains to me precisely.

Mike

Some things to check

1) Is the SQL Server authentication mode in Mixed mode? You are trying to connect using standard security
2) Has the NT login that the web app uses expired? Is the account locked out
3) Can you fire up Query Analyzer and connect to the database from the client using the login credentials in your connection string

Sorry I don't have answers, just a load of more questions! :-

-
Mark Allison, SQL Server MV

You can go through the steps in this article:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306

Also, which user is listed in the login failed message can make a big
difference in the troubleshooting steps. Null indicates a domain
controller/authentication issue, ntauthority\anonomous could be an SPN/SSPI
problem. A SQL account indicates you are using SQL auth and the SQL Server
is configured to only accept Windows authentication.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Mark: Thanks for your suggestions! I've connected by specifying SQL
Authorization, but still can't connect with Windows Authorization, which
I prefer, for simplified coding. You've helped me get one step further,
however!



*** Sent via Developersdex http://www.developersdex.com ***

Cindy: Thanks for your suggestions! I've been able to connect by
specifying SQL Authorization, but still can't connect by Windows
Authorization, which I prefer, for simplified coding. Cheers!



*** Sent via Developersdex http://www.developersdex.com ***

Can you make other connections to the server that SQL Server is installed
on? Can you get to shares on that machine? It may be that either your
Windows account cannot be authenticated or that your Windows account is
denied permission to access that machine from the network.

Have you tried various protocols (np:servername, tcp:servername)?

What is the exact error you get now for Windows authentication? Do you get
the same error from OSQL, ISQL, Query Analyzer?

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.