sql server login 2

[unicorn11]

i have a asp connection into a sql server called as Server
for a site that i created it was working perfectly till

I ran a Sql server 7 service pack 3

then from login that was working before the update suddenly started giving this


[red]Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'SERVER\IUSR_TRIPMEDIA-1'.
connect.asp, line 6[/red]

i even tried running the sa account but error

but it is connecting through the Query Analyser

regards Unicorn11
unicorn11@mailcity.com

[red]Luck is not chance, it's toil; fortune's expensive
smile is earned.[red]

 

[Drtheater]

go to IIS, virtual directory properties, security and uncheck anonymous login

good luck

 

[unicorn11]

Hi Drtheater

Thanks it helped

regards Unicorn11
unicorn11@mailcity.com

[red]Luck is not chance, it's toil; fortune's expensive
smile is earned.[red]

 

[GlennBSI]

I realize you got this to work with Drtheater's suggestion, but I'm trying to understand what all happened here.

What I get (I think) is that the login was being attempted by the IUSR account, which didn't work and that by removing allow anonymous, apparently challenge/response is now passing the logged in user's nt account to the SQL Server and now that works.

But you said you tried (unsuccessfully) to connect using the sa account, but it worked before the service pack install. Not seeing the connection method (connect string), I'm at a loss. Why wouldn't that work and what did the service pack install do to mess it up?

What do you mean by "called as Server"? Would you mind showing me the connect string you are using?

I really want to understand this.

Thanks!!

 

[unicorn11]

Here is the connection string

Con.Open "DRIVER={SQL Server};SERVER=server;DATABASE=sabedata;UID=user;PWD=password;"

Regards Unicorn11
unicorn11@mailcity.com

[red]Luck is not chance, it's toil; fortune's expensive
smile is earned.[red]