August 10, 2009 at 11:20 am
Having a problem with users connecting...
We have windows groups set up as logins such as
Domain\U1B-123
Domain\U1B-456
Domain\U1B-789
They are users in various databases such as
db1 ... U1B-123
db2 ... U1B-123
db1 ... U1B-456
db3 ... U1B-456
db1 ... U1B-789
We previously had 456's default db set to db1.
All other logins use db2 as default.
We pointed 456's default to db2 as well, then we take db1 offline.
Now, everyone that is a member of 456 cannot connect to the server. The specific error msg: ""
The server principal "DOMAIN\U1B-456" is not able to access the database "db1" under the current security context.
My disconnect here is, why is it looking at db1 in the first place? :unsure:
Honor Super Omnia-
Jason Miller
August 10, 2009 at 12:51 pm
How are the users connecting to the database? is this an application using ODBC/OLEDB, SSMS, something else?
Is it possible that there needs to be a change on the user side as it may still be pointing to DB1?
August 10, 2009 at 12:54 pm
They are connecting in a number of ways, each fails.
I'm testing it using
"EXECUTE AS LOGIN = 'DOMAIN\UserX'
blah blah...
When a 'real' user tries SQL Management Studio, it fails with the same message.
As does the .NET application they're trying to use.
Honor Super Omnia-
Jason Miller
August 10, 2009 at 1:02 pm
Bear with me, have you checked to see wha the system table says:
select * from sys.server_principals
I can't recreate your problem, so I am having to guess here.
August 11, 2009 at 4:47 am
Lynn Pettis (8/10/2009)
Bear with me, have you checked to see wha the system table says:select * from sys.server_principals
Not sure what you're looking for...
But...
Name: U1B-456
Principal_ID 355
sid 0x0000
Type G
Type_Desc WINDOWS_GROUP
is_disabled 0
create_date 20090715
modify_date 20090715
default_database_name MASTER
default_language_name us_english
credential_id
Neat huh?
Honor Super Omnia-
Jason Miller
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply