Re: Error 21776:
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 3 Aug 2006 07:50:15 -0500
Anyone ever see this sort of behavior?
Yes, this is normal. The GUI object browser caches data for performance
reasons. When changes are made externally, you need to manually refresh the
tree by right-clicking and selecting refresh.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"A McGuire" <allen.mcguire@xxxxxxxxxxxxxxxxx> wrote in message
news:uwaWqeatGHA.1888@xxxxxxxxxxxxxxxxxxxxxxx
I'm doing the following:
use master
exec sp_grantlogin 'DOMAIN\ug_ITSec_SQL'
exec sp_addsrvrolemember 'DOMAIN\ug_ITSec_SQL', 'securityadmin'
Then after, trying to grant that new login db_owner permissions, for
example, by running the following:
use master
go
exec sp_grantdbaccess 'DOMAIN\ug_ITSec_SQL', 'ug_ITSec_SQL'
exec sp_addrolemember 'db_owner','ug_ITSec_SQL'
However, when I then click on the Login and check out the database access,
I get the following strange error:
"Error 21776: [SQL-DMO] The name 'ug_ITSec_SQL' was not found in the Users
collection. If the name is a qualified name use [] to seprate the various
parts of the name, then try again."
However, once I go to the individual database - master in this case, and
click on the User, view it, close it, and go back to the Login... it is
all cleared up. As if clicking and viewing the User in the database
cleared something up?
Anyone ever see this sort of behavior?
.
- References:
- Error 21776:
- From: A McGuire
- Error 21776:
- Prev by Date: Re: Orphaned user owns objects as dbo and cannot be dropped.
- Next by Date: Re: Schema Problems
- Previous by thread: Re: Error 21776:
- Next by thread: restoring database when guest account is missing
- Index(es):
Relevant Pages
|
|
