Topics Topics Edit Profile Profile Help/Instructions Help Member List Member List  
Search Last 1|3|7 Days Search Search Tree View Tree View  

SQL User trapped inside and he can't ...

Blackthorne Discussion Group » Blackthorne Pro » Archive through August 04, 2010 » SQL User trapped inside and he can't get out! « Previous Next »

  ClosedClosed: New threads not accepted on this page Last Poster Posts Pages Last Post
  ClosedClosed: New threads not accepted on this page        

Author Message
Top of pagePrevious messageNext messageBottom of page Link to this message

Dustin Carlson (fishwest)
New member
Username: fishwest

Post Number: 3
Registered: 02-2010
Posted on Wednesday, July 28, 2010 - 04:41 pm:   Edit Post Delete Post Print Post

Hi-

This is probably more of a SQL question than it is a BT questions, but here goes:

When I try to add a user (that does exist in the SQL logins folder), I get an error that "The login already has an account under a different user name." I have attached a screenshot of the error. I guess what I am asking for is...is there a way to clean that user out?

Thank you!

Dustin
Fishwestscreenshot of error
Top of pagePrevious messageNext messageBottom of page Link to this message

Clark Frazier (cfrphoto)
Senior Member
Username: cfrphoto

Post Number: 2533
Registered: 03-2005


Posted on Wednesday, July 28, 2010 - 07:59 pm:   Edit Post Delete Post Print Post

Dustin,

I don't know for sure how this may have occurred. The following link may be useful: http://social.msdn.microsoft.com/forums/en-US/sqlsecurity/thread/9faf79d0-f4b6-4b6c-9505-68cd2ec636af/ or you can execute the following SQL from a SQL Server Management Studio Query Window:

sp_helplogins 'domain\account'

It appears that you may have set some SQL Server administrative accounts. Instead, I would recommend setting up your Windows login (using integrated security) as the administrator and do not assign SQL Server user accounts more privileges than necessary for running Blackthorne using the BTData database. Also, check schema ownership. Absent a compelling reason, it should always be dbo to avoid problems with multi-user database access.

Clark
cfrphoto

Administration Administration Log Out Log Out   Previous Page Previous Page Next Page Next Page