Re: Trusted connection error
From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 02/25/04
- Next message: Keith Wilson: "Re: Yukon: Password Validation Failed"
- Previous message: Duncan: "Re: Security Patches for 64-bit SQL Server 2000"
- In reply to: Dave Uphoff: "Trusted connection error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 25 Feb 2004 08:11:20 -0600
To add to Hari's response, if your requirement is to use SQL Server
authentication rather than Windows authentication, your SQL Server needs to
be configured to allow both SQL Server and Windows authentication.
Windows-only is the installation default.
You can change the configuration using Enterprise Manager under Server
properties --> Security. You'll need to restart SQL Server after you make
the change.
-- Hope this helps. Dan Guzman SQL Server MVP "Dave Uphoff" <anonymous@discussions.microsoft.com> wrote in message news:0fe501c3fb56$568594a0$a301280a@phx.gbl... > I get the following error when attempting to connect to > an SQL database. > > Login failed for user 'dave'. Reason: Not associated with > a trusted SQL Server connection. > > This is my connection string. > > "Provider=SQLOLEDB; Data Source=localhost;Initial > Catalog=subscriber;User ID=dave;Password=******"; > > Can anyone tell me what why I get this error? I have > dave established as a Data User for the database. > Dave Uphoff >
- Next message: Keith Wilson: "Re: Yukon: Password Validation Failed"
- Previous message: Duncan: "Re: Security Patches for 64-bit SQL Server 2000"
- In reply to: Dave Uphoff: "Trusted connection error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
