Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Domain Users Db access, weird behaviour

Author  Topic 

dpoletto
Starting Member

3 Posts

Posted - 2008-05-12 : 08:32:08
hi,
i have a really annoying problem with one of our customers, he is using SQL2000.
Our app. uses 2 dbs, connecting to them through ODBC, trusted auth.

Often the customer calls me because, when he tries to use the application (by entering username and password) after some seconds he gets an error message like "User does not have access to any database to this server location".

If i look on the dbserver, "DOMAIN USERS" have access to all the databases needed by the application, but only after removing and re-assigning the access to our db (with public and db_owner roles, like before) everything works fine for some days.

Any ideas?

Thank you for the help.
Damiano

A good plan violently executed right now is far better than a perfect plan executed next week. (Patton, George S.)

TG
Master Smack Fu Yak Hacker

6065 Posts

Posted - 2008-05-12 : 11:11:50
>>Any ideas?
One thought: is it possible that the DBs are being restored from another server instance. When that happens the db user SID is could be out of sync with the server login SID.

Be One with the Optimizer
TG
Go to Top of Page

dpoletto
Starting Member

3 Posts

Posted - 2008-05-14 : 02:54:38
the DBs are not restored, they are just "running" on that server instance.
The event viewer of the server doesnt show any interesting event, i think it could be something wrong with the SQL server instance but, except for that problem, everything is fine

A good plan violently executed right now is far better than a perfect plan executed next week. (Patton, George S.)
Go to Top of Page

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2008-05-14 : 10:28:36
That message is not like any SQL Server message I have seen before. Is it possible that a restart of the SQL Server is cutting all of the application's connections to the database until the application itself is restarted? The message sounds almost like a catch-all message to me.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-05-14 : 23:41:00
Is it domain account? Did sql server lose communication to domain controller?
Go to Top of Page

dpoletto
Starting Member

3 Posts

Posted - 2008-05-19 : 03:48:56
today it happened again. :(
DOMAIN USERS is the domain users group.
This time it was a little different, only one db had this problem, as usual nothing suspicious both in event viewer and in sql server logs.
I've found a little difference on the 2 dbs that have this problem: in the "Login property window", in the "database access" tab, in the rows corresponding to ours DBs the account is listed as "DOMAIN USERS" instead of "MYDOMAIN\DOMAIN USERS". by removing and then adding again the account from the database users list (instead from the server login list) now the difference is fixed, but i don't know if it's the solution.

A good plan violently executed right now is far better than a perfect plan executed next week. (Patton, George S.)
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-05-19 : 22:53:13
>> the account is listed as "DOMAIN USERS" instead of "MYDOMAIN\DOMAIN USERS".

Not the issue if it maps to correct sql login MYDOMAIN\DOMAIN USERS.
Go to Top of Page
   

- Advertisement -