Permissions problem on SBS 2003 R2 for SQL Server 2005 clients
- From: John Hackert <hackertjohnb@xxxxxxxxx>
- Date: Thu, 07 Jun 2007 18:06:55 -0700
I've been attempting to troubleshoot the following permissions problem
involving SQL Server Express 2005 on a Windows SBS 2003 R2 network.
Let me apologize that what follows is reposted from the
microsoft.public.sqlserver.server group, as it did not happen to
receive a response:
I've been testing a SQL Server 2005 Express database in a multiuser
environment using Window Small Business Server 2003 R2 with Windows XP
service pack 2 on the clients. The database in question is under the
default "SQL Server Express" instance. Security is Windows
Authentication.
Client connection to the database via SSMSE was able to be established
without difficulty using the surface area configuration utilities,
with a catch that I can't understand.
On a given client computer to which I may have logged on with Windows
administrator privileges, after connecting to the database via SSMSE,
the connection icon changes from the empty white circle to the green
circle with a white arrowhead and all database elements are
accessible, as expected.
However, when I logon to Windows SBS on a client computer with a test-
user not bearing administrator privileges (as of course intended), a
phenomenon occurs that I cannot understand or resolve: the client is
able to "connect" to the database via SSMSE, in that the connection
dialogue is successful and, once again, all database elements are
accessible (tables may be opened directly and their data modified,
stored procedures may be executed successfully, etc.). However, the
status icon remains an empty white circle, not a green circle with a
white arrowhead.
The reason this "pseudo-connected" status is a problem in my
particular case is that I am using an ADP which behaves erratically
with respect to recordsources whenever the green circle/white
arrowhead is absent. I apologize that this is essentially a re-post,
as I initially began to seek assistance with this problem via the
microsoft.public.access.adp.sqlserver group (see the "Recordsource
only available to Administrator on clients" post for specific details
of the ADP behavior).
By adjusting user permissions in the SBS 2003 console, I believe I
have isolated the apparent permissions problem to the "Domain Admins
Group": if a non-administrator user is added to this group, the
problem goes away; any Administrator is of course natively a member of
this group.
Because it will not be practical to grant administrator privileges to
clients, I would be grateful for any insight on this phenomenon.
.
- Follow-Ups:
- Re: Permissions problem on SBS 2003 R2 for SQL Server 2005 clients
- From: bass_player [SBS-MVP]
- Re: Permissions problem on SBS 2003 R2 for SQL Server 2005 clients
- Prev by Date: Re: 2003 R2 expanded licensing rights
- Next by Date: rww accessing companyweb
- Previous by thread: Re: 2003 R2 expanded licensing rights
- Next by thread: Re: Permissions problem on SBS 2003 R2 for SQL Server 2005 clients
- Index(es):
Relevant Pages
|
