Re: Error 21002: [ SQL-DMO] User "xxxxx" already exists.

From: Dan Guzman (danguzman@nospam-earthlink.net)
Date: 03/13/03 

From: "Dan Guzman" <danguzman@nospam-earthlink.net>
Date: Wed, 12 Mar 2003 20:27:46 -0600

I haven't seen this behavior before. Assuming you are using Enterprise
Manager, it looks like EM isn't refreshing the collections properly as
you make modifications.

What version and service pack of SQL Server are you running? Please
provide the exact steps you took to produce the error. 

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
"Mukul Agochiya" <magochiya@yahoo.com> wrote in message
news:008601c2e8b8$157fd1c0$a301280a@phx.gbl...
> 1. No restoration of database was performed.
> 2. I do not see that user account as orphaned.
>
> But real issue is that this new user account is not being
> saved with necessary permissions for the selected database.
>
> Mukul
>
> >-----Original Message-----
> >Was the user database restored or attached?  In this
> case, you may have
> >orphaned users.  You can remedy this with
> sp_change_users_login.
> >Alternatively, you can drop the user from the database
> using
> >sp_revokedbaccess from Query Analyzer.
> >See the Books Online for details.
> >
> >-- 
> >Hope this helps.
> >
> >Dan Guzman
> >SQL Server MVP
> >
> >-----------------------
> >SQL FAQ links (courtesy  Neil Pike):
> >
> >http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> >http://www.sqlserverfaq.com
> >http://www.mssqlserver.com/faq
> >-----------------------
> >
> >"Mukul Agochiya" <magochiya@yahoo.com> wrote in message
> >news:085901c2e8b3$50bba520$a501280a@phx.gbl...
> >> I created a new user where we logged as 'SA'. I assigned
> >> permissions to certain databases. While saving it, I got
> >> this error message:
> >>
> >> Error: 21002: [ SQL-DMO] User "xxxxx" already exists.
> >>
> >> Can you please let me know how to resolve this. I know
> >> that we can grant permissions using T-SQL.
> >>
> >> Secondly, if we delete this newly created user account,
> >> then it is still visible under different user roles
> >> defined earlier. It does not delete the user account
> from
> >> the roles completely.
> >>
> >> I will appreciate if somebody can give hint how to
> resolve
> >> these issues.
> >>
> >> Mukul
> >
> >
> >.
> >

Relevant Pages

  • ADP, Application Role, and objects
    ... The above link is to an atricle on how to implement SQL Server Application ... After you connect with your ADP, fire a bit of code to set the ... third party tools to view the data on the same database. ... Scenario 1 - If I explicitly grant permissions on that object to the user ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Execute Persmission denied on object sp_OACreate
    ... > SQL Server is creating a job behind the scenes. ... > permissions. ... > SA account password and gaining access to the database. ... >>> How can get a user permissions to execute these stored procedures ...
    (microsoft.public.sqlserver.security)
  • Re: Newbie: I dont understand user permissions for table access
    ... > My database is remote to my workstation. ... > tables/fields WITHOUT specifying anything in the permissions dialogs? ... >> HOW are you connecting to SQL Server? ... what rights/permissions have been granted to the PUBLIC role? ...
    (microsoft.public.sqlserver.server)
  • Re: Execute Persmission denied on object sp_OACreate
    ... SQL Server is creating a job behind the scenes. ... SA account password and gaining access to the database. ... > SQL Server doesn't check permissions on indirectly referenced objects as ... > the proxy account security context for non-sysadmin users from Enterprise ...
    (microsoft.public.sqlserver.security)
  • Re: Security question ..
    ... What I want to prevent is any access to the database accept through our ... application unless you have elevated permissions. ... Authentication, if he is smart enough to create an NT Auth ODBC connection ... passes through to the database or to use SQL Server authentication. ...
    (microsoft.public.sqlserver.server)