by Hi.
When I try to add a new user I'm getting error described below, but the
workaround didn't work for me.
New user can't login and can't be dropped. When trying to make any changes
to a new user I just created I'm getting the same errors(21770, 15175). I
have run DBCC CHECKDB ( 'database_name' ) on al DB's to no avail. I run MS
SQL 6.5 SP5 on WinNT3.51 SP5. I'll appreciate any suggestions.
Thanx,
Mark
http://support.microsoft.com/support/kb/articles/q223/9/99.asp
BUG: Error 21770 Adding Login in SEM and User with SP_ADDUSER
The information in this article applies to:
Microsoft SQL Server version 6.5
SYMPTOMS
After you grant database access through sp_adduser to a login that was
created using Enterprise Manager, the following error message (Error 21770)
occurs when you edit the login in Enterprise Manager:
The name <username> was not found in the Users collection.
If you delete the user from the database and then try to drop the login, the
following error message might appear (Error 15175):
<SQL Server> Login 'user' is aliased or mapped to a user in one or more
database(s). Drop user or alias before dropping login.
WORKAROUND
To work around this problem, do one of the following:
When you add the login in SQL Enterprise Manager, specify a default database
and a permit database.
In Enterprise Manager, expand
Servername/Databases/databasename/Groups/Users. Right-click Public and click
refresh.
STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5.
MORE INFORMATION
Steps to Reproduce Behavior
1. In the SQL Enterprise Manager, define a new login (for example, user1).
2. Open a query window, chose pubs as the database, and run the following
code:
sp_adduser user1, user1
SQL Server returns the following message: "New user added."
3. Go to Enterprise Manager, and refresh Logins.
4. Double-click user1 login.
RESULT: The following error message appears:
Error 21770: The name 'user1' was not found in the Users collection.
You might also experience this error when you try to edit permissions for
the user.
This error also occurs when adding a login through sp_addlogin.
--
Mark Nowaczyk