When trying to load the mainpage, Default.aspx, the following error is 
generated:

Error Message: Login failed for user 'sa'. Reason: Not associated with a 
trusted SQL Server connection.

Using SQL 2000 (Demo) Enterprise Manager, the database 'thePhile' does 
exist, and two users are listed:

dbo -> login: sa, access: Permit
ThePhileMaster -> login: [null], access: Permit

Perhaps someone can suggest a fix.

Thanks,

Andrew Pasetti

This is because you are attempting to login to SQL Server using a SQL
Server login but have SQL Server setup to only allow authentication
using Windows domain accounts.

To correct this, you can either login to SQL Server using a Windows
domain account OR configure SQL Server to allow SQL Server
authentication. To do this, open the Enterprise Manager, right click on
the server itself, select properties, the security tab, and then be sure
SQL Server and Windows authentication is selected and not the Windows.

-----Original Message-----
From: Andrew Pasetti [mailto:andrewpasetti@y...] 
Sent: Thursday, July 11, 2002 14:56
To: Website Programming with ASP.NET
Subject: [aspdotnet_website_programming] Error: Login failed for user
'sa'

When trying to load the mainpage, Default.aspx, the following error is 
generated:

Error Message: Login failed for user 'sa'. Reason: Not associated with a

trusted SQL Server connection.

Using SQL 2000 (Demo) Enterprise Manager, the database 'thePhile' does 
exist, and two users are listed:

dbo -> login: sa, access: Permit
ThePhileMaster -> login: [null], access: Permit

Perhaps someone can suggest a fix.

Thanks,

Andrew Pasetti

I think there may be more to it ... ...

After installing and successfully using the ThePhile for a few weeks back 
in April .. I left it alone in may and june ... with lots of other .net 
activity in the meantime (Matrix, Favorites2, critical updates, etc.).

When I went to run it again in july, and got the same error as reported 
below ... but sa is in and unchanged, the security is both (unchanged as 
far as I know), etc.

I think one of microsoft critical updates or some other install may have 
changed the server so that something else has to be done to get it working 
again ... haven't found the problem/solutionyet, but will report it when I 
do.


I was surpprised to see someone else with the same problem .. but the 
solution below is not the solution for my case.

> This is because you are attempting to login to SQL Server using a SQL
Server login but have SQL Server setup to only allow authentication
using Windows domain accounts.

To correct this, you can either login to SQL Server using a Windows
domain account OR configure SQL Server to allow SQL Server
authentication. To do this, open the Enterprise Manager, right click on
the server itself, select properties, the security tab, and then be sure
SQL Server and Windows authentication is selected and not the Windows.

-----Original Message-----
From: Andrew Pasetti [mailto:andrewpasetti@y...] 
Sent: Thursday, July 11, 2002 14:56
To: Website Programming with ASP.NET
Subject: [aspdotnet_website_programming] Error: Login failed for user
'sa'

When trying to load the mainpage, Default.aspx, the following error is 
generated:

Error Message: Login failed for user 'sa'. Reason: Not associated with a

trusted SQL Server connection.

Using SQL 2000 (Demo) Enterprise Manager, the database 'thePhile' does 
exist, and two users are listed:

dbo -> login: sa, access: Permit
ThePhileMaster -> login: [null], access: Permit

Perhaps someone can suggest a fix.

Thanks,

Andrew Pasetti

Believe it or not ... it fixed itself ... it just started to work all on 
its own ...  heck of a way for an OS and framework to operate .. whatever 
happened to determinism in software :)


> I think there may be more to it ... ...

> After installing and successfully using the ThePhile for a few weeks 
back 
i> n April .. I left it alone in may and june ... with lots of other .net 
a> ctivity in the meantime (Matrix, Favorites2, critical updates, etc.).

> When I went to run it again in july, and got the same error as reported 
b> elow ... but sa is in and unchanged, the security is both (unchanged as 
f> ar as I know), etc.

> I think one of microsoft critical updates or some other install may have 
c> hanged the server so that something else has to be done to get it 
working 
a> gain ... haven't found the problem/solutionyet, but will report it when 
I 
d> o.

> 
I>  was surpprised to see someone else with the same problem .. but the 
s> olution below is not the solution for my case.

Well, we travel around the country speaking on .NET, SQL Server, and
other products for Microsoft, AppDev, asp.netPRO, and others (just so
you don't think I gave a flaky answer) and this is the common textbook
error message received when the security setting in SQL Server is set to
allow Windows only authentication. I haven't had an authentication
problem other than that or receive this error in any other scenario.
However, these are huge technologies. No telling what could happen.
Sorry that the answer didn't fix your problem.

-----Original Message-----
From: Frank Kurka [mailto:wrox@f...] 
Sent: Saturday, July 13, 2002 13:55
To: Website Programming with ASP.NET
Subject: [aspdotnet_website_programming] RE: Error: Login failed for
user 'sa'

Believe it or not ... it fixed itself ... it just started to work all on

its own ...  heck of a way for an OS and framework to operate ..
whatever 
happened to determinism in software :)


> I think there may be more to it ... ...

> After installing and successfully using the ThePhile for a few weeks 
back 
i> n April .. I left it alone in may and june ... with lots of other
.net 
a> ctivity in the meantime (Matrix, Favorites2, critical updates, etc.).

> When I went to run it again in july, and got the same error as
reported 
b> elow ... but sa is in and unchanged, the security is both (unchanged
as 
f> ar as I know), etc.

> I think one of microsoft critical updates or some other install may
have 
c> hanged the server so that something else has to be done to get it 
working 
a> gain ... haven't found the problem/solutionyet, but will report it
when 
I 
d> o.

> 
I>  was surpprised to see someone else with the same problem .. but the 
s> olution below is not the solution for my case.

Hey, no apologies needed, it was a great clue ... maybe it helped the 
first poster ... but it will be the first thing I double check in the 
future .. thanks for helping ....