Re: login failed for sql server
From: John M Deal (johndeal_at_necessitysoftware.com)
Date: 11/24/04
- Next message: Nick V.: "RE: WHERE IN() with parameters"
- Previous message: Sahil Malik: "Microsoft Data Access Application Block !!!!"
- In reply to: rbutch_at_coair.com: "login failed for sql server"
- Next in thread: Jeff Dillon: "Re: login failed for sql server"
- Reply: Jeff Dillon: "Re: login failed for sql server"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Nov 2004 07:21:25 -0800
I can't swear to it but I think using SSPI and a User Id are mutually
exclusive (someone please correct me if I'm wrong). I'd start by trying
to eliminating each in turn and seeing if one or the other succeeds.
Oh, and be sure the username and password are for a Sql user that has
permissions not a Windows user.
Also you didn't mention what kind of client this is running under. If
you are running under a web service, IIS, or an NT service you will see
interesting results when trying to use SSPI. The reason is that each of
the mentioned application types are not running as you but instead as
whatever identity their underlying service is running as. You may
already know that but I figured it was worth mentioning.
I also seem to remember having this issue if my Sql Server instance was
not setup to support Mixed security. You may want to check and see if it
does (seeing as how mixed is required if you want to go back and forth
between SSPI and specifying a logon and password).
Hope something in there helps.
Have A Better One!
John M Deal, MCP
Necessity Software
rbutch@coair.com wrote:
> guys, i cant figure this out. ive even hardcoded the user name in the connection string.
> im an admin on the box, im the full fledged dbo on the instance on the server.
> is anyone familiar with this.
> it refers to null, but its definately in there.
>
> here's the connection string:
>
> workstation id=HQJ1759DX;packet size=4096;user id=coE7599;integrated security=SSPI;data source=HQJ1750C;persist security info=False;initial catalog=MY_DB
>
>
> here's the error
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection
>
> **********************************************************************
> Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
- Next message: Nick V.: "RE: WHERE IN() with parameters"
- Previous message: Sahil Malik: "Microsoft Data Access Application Block !!!!"
- In reply to: rbutch_at_coair.com: "login failed for sql server"
- Next in thread: Jeff Dillon: "Re: login failed for sql server"
- Reply: Jeff Dillon: "Re: login failed for sql server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|