July 5, 2007 at 5:54 am
Hi all,
I am a newbie and have a issue,which obviously for you is trivial-for me it would be great if you could help me.
I created a LOGIN in SQL 2005 which fails when logging in with:
TITLE: Connect to Server
------------------------------
Cannot connect to localhost.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user 'bkovac'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452
------------------------------
1.I created a LOGIN login1,set SQL authentication with password,default db-master;
2.created a new user for my database,set the database role to db_owner;
3.finally done the user mapping for that LOGIN;
4.I checked that the SQL server allows mixed authentication mode and restarted the server.
Now can anyone give me a point where to start with?
PS:I checked the error no. on the net,which was suggesting the authentication is set only to Windows mode.
Please help me
Many thanks
Ben
July 5, 2007 at 6:17 am
This error occurs if you try to login thru a SQL server id which has its authntication mode set to windows. Are you sure the server runs in mixed mode. Thjis can be checked by viewing the properties of the server and looking in the security part. I hope so still he mode is windows and not mixed.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 5, 2007 at 6:22 am
Hi Sugesh,
Yes I know, that was my first thought,clicked on the SQL server->Properties->Security and changed to SQL and Windows Authentication mode.Then restarted SQL, tried to log on and failed withe the error mentioned from earlier.
July 5, 2007 at 7:29 am
What are you logging in from? From your other recent posts here, I assume you are accessing SQL Server from Excel, then you must be using ADO or ODBC? Then, check the connection settings is not set for IntegratedSecurity, and has the userid and pwd parameters you expect.
Hope this helps
Mark
July 5, 2007 at 7:59 am
Hi Mark,
This is not related to my previous posts, simply just created a LOGIN account for logging in to SQL Management Studio, also created a user and mapped it to a specific database as the database owner.
Ben
July 5, 2007 at 8:18 am
Can you post the properties of the login. Either from SSMS or from syslogins view.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 5, 2007 at 8:48 am
Hi Sugesh,
Here are my syslogin properties:
sid-0x08BDEBF1DD75AA48818724C2632A96A8
status-9
createdate-2007-07-05 12:26:20.403
updatedate-2007-07-05 15:34:10.477
accdate-2007-07-05 12:26:20.403
totcpu-0
totio-0
spacelimit-0
timelimit-0
resultlimit-0
name-bkovac
dbname-master
password-#########
language-us_english
denylogin-0
hasaccess-1
isntname-0
isntgroup-0
isntuser-0
sysadmin-0
securityadmin-0
serveradmin-0
setupadmin-0
processadmin-0
diskadmin-0
dbcreator-0
bulkadmin-0
loginname-bkovac
Cheers,
Ben
July 5, 2007 at 11:23 pm
Just give this user sysadmin permission and check if that succeeds. All parameters are right but looks weird.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 6, 2007 at 7:26 am
Hi Sugesh,
Added the user to the sysadmin role and it works now.
So does this mean that without SysAdmin server role it won't work?Thanks
Cheers
Ben
July 9, 2007 at 7:50 am
I tried to recreate this issue on one of my servers and did not have the issue. But I am also running SP2. I did find this pre-SP1 bug though:
http://support.microsoft.com/kb/925744/
It seems to describe the issue you are having. Perhaps you're still on SP1 or less?
July 12, 2007 at 2:18 pm
Rich,
I am bouncing my head against the wall!
Installed the SP2 and the problem is just...dissappeared!
Rich, Sugesh and all of you guys thank you very much, very appreciate your time and help
Ben
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply