| Author |
Topic |
|
iceblizzard
Starting Member
17 Posts |
Posted - 2007-01-03 : 02:06:21
|
| Login failed for user ''. The user is not associated with a trusted SQL Server Connection.Ive got this error... I have just installed the SQL Server 2005 Standard Edition. Could anyone encounter and solve this problem.. please til me how to solve this. I google this but couldnt find a reliable solution for this..Thanx...!-------------------Real Programmer dont documentIf its hard to write Thenits easy to undertand.End If |
|
|
harsh_athalye
Master Smack Fu Yak Hacker
5581 Posts |
Posted - 2007-01-03 : 02:54:31
|
| Which mode you are using for connecting? Windows or SQL Server?Harsh AthalyeIndia."The IMPOSSIBLE is often UNTRIED" |
 |
|
|
iceblizzard
Starting Member
17 Posts |
Posted - 2007-01-03 : 04:40:56
|
| Windows-------------------Real Programmer dont documentIf its hard to write Thenits easy to undertand.End If |
 |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2007-01-03 : 06:24:06
|
| Locally or remote? Same domain?-------Moo. :) |
 |
|
|
iceblizzard
Starting Member
17 Posts |
Posted - 2007-01-08 : 00:16:37
|
| Using Windows... using same domain.. locally-------------------Real Programmer dont documentIf its hard to write Thenits easy to undertand.End If |
 |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-01-08 : 01:57:53
|
Did you create a sql login associated with the windows account you are connecting with?What app is raising this error? SSMS, or something you wrote yourself? www.elsasoft.org |
 |
|
|
iceblizzard
Starting Member
17 Posts |
Posted - 2007-01-08 : 04:30:40
|
| hello, I initially solve the 2nd part of the error.. Now, when i run a test, It only says "Login failed for user 'sa'".-------------------Real Programmer dont documentIf its hard to write Thenits easy to undertand.End If |
 |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-01-08 : 10:02:50
|
that's probably because you are trying login as SA but are using the wrong password. In any case you should never use the SA account. it's too powerful - you'll end up shooting yourself in the foot. Plus it's a security risk because it means you'll have the sa password lying around in config files. www.elsasoft.org |
 |
|
|
iceblizzard
Starting Member
17 Posts |
Posted - 2007-01-09 : 00:00:56
|
| I have it configured correctly... but when sa is used in logging in to SQL Server Management Studio, its ok. but when running in our application and connect to DB, it fails..-------------------Real Programmer dont documentIf its hard to write Thenits easy to undertand.End If |
 |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-01-09 : 12:27:37
|
so you are connecting as SA from your app??? that's pretty dangerous. www.elsasoft.org |
 |
|
|
iceblizzard
Starting Member
17 Posts |
Posted - 2007-01-10 : 00:45:13
|
| Yeah... I know its risky. But what else can I do, they configured it that way... I can only pair it.-------------------Real Programmer dont documentIf its hard to write Thenits easy to undertand.End If |
 |
|
|
|