I have a SQL Server running on a new W2k3 Server, and a user that received
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
Nuno
Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:
> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>
|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:
Showing posts with label manage. Show all posts
Showing posts with label manage. Show all posts
Friday, February 24, 2012
Can't manage SQL
I have a SQL Server running on a new W2k3 Server, and a user that received
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
NunoThe starting and stopping of a Server Service has nothing
to do with SQL and everything to do with the W2k3 roles.
So the problem here is your user does not have access
rights to stop the service as the W2k3 role will not let
them.
Have a chat to your server guys.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I have a SQL Server running on a new W2k3 Server, and a
user that received
>the Sys Admin roles at this SQL Server. However, this
user can't access this
>SQL Server using the Service Manager nor stop/pause this
server. The others
>operations, suck as creating a new DB is ok for this
group. Any help?
>the error that i get is "error 5 (acess denied)"
>thanks
>Nuno
>.
>|||Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:
> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:
> > I have a SQL Server running on a new W2k3 Server, and a user that received
> > the Sys Admin roles at this SQL Server. However, this user can't access this
> > SQL Server using the Service Manager nor stop/pause this server. The others
> > operations, suck as creating a new DB is ok for this group. Any help?
> >
> > the error that i get is "error 5 (acess denied)"
> >
> > thanks
> >
> > Nuno
> >
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
NunoThe starting and stopping of a Server Service has nothing
to do with SQL and everything to do with the W2k3 roles.
So the problem here is your user does not have access
rights to stop the service as the W2k3 role will not let
them.
Have a chat to your server guys.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I have a SQL Server running on a new W2k3 Server, and a
user that received
>the Sys Admin roles at this SQL Server. However, this
user can't access this
>SQL Server using the Service Manager nor stop/pause this
server. The others
>operations, suck as creating a new DB is ok for this
group. Any help?
>the error that i get is "error 5 (acess denied)"
>thanks
>Nuno
>.
>|||Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:
> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:
> > I have a SQL Server running on a new W2k3 Server, and a user that received
> > the Sys Admin roles at this SQL Server. However, this user can't access this
> > SQL Server using the Service Manager nor stop/pause this server. The others
> > operations, suck as creating a new DB is ok for this group. Any help?
> >
> > the error that i get is "error 5 (acess denied)"
> >
> > thanks
> >
> > Nuno
> >
Can't manage a remote SQL Server
I have a SQL Server running on a new W2k3 Server, and a group in the AD
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?
What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?
What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Can't manage a remote SQL Server
I have a SQL Server running on a new W2k3 Server, and a group in the AD
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Can't manage a remote SQL Server
I have a SQL Server running on a new W2k3 Server, and a group in the AD
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Sunday, February 12, 2012
Can't get to where to manage roles
Yesterday, I was able to go to http://localhost/reports and manage roles and
users in those roles.
Today, that page looks different. I'm not sure if anyone ran anything or
what, but I now just see links for various projects.
I noticed in IIS that there is a pages/roles.aspx page so I typed
http://localhost/reports/pages/roles.aspx and I did see the list of roles.
But when I click on "Browsers" it tells me the IUSR account does not have
permissions.
What's going on? Shouldn't I be able to get to roles without having to know
the .aspx page? Where are the links for this?
I'm so confused. Thanks for any help.
RonNevermind. I needed to set anonymous access to off in both Reports and
ReportServer.
"Ronald S. Cook" <rcook@.westinis.com> wrote in message
news:%23oPNn$pWHHA.600@.TK2MSFTNGP05.phx.gbl...
> Yesterday, I was able to go to http://localhost/reports and manage roles
> and users in those roles.
> Today, that page looks different. I'm not sure if anyone ran anything or
> what, but I now just see links for various projects.
> I noticed in IIS that there is a pages/roles.aspx page so I typed
> http://localhost/reports/pages/roles.aspx and I did see the list of roles.
> But when I click on "Browsers" it tells me the IUSR account does not have
> permissions.
> What's going on? Shouldn't I be able to get to roles without having to
> know the .aspx page? Where are the links for this?
> I'm so confused. Thanks for any help.
> Ron
>
>
users in those roles.
Today, that page looks different. I'm not sure if anyone ran anything or
what, but I now just see links for various projects.
I noticed in IIS that there is a pages/roles.aspx page so I typed
http://localhost/reports/pages/roles.aspx and I did see the list of roles.
But when I click on "Browsers" it tells me the IUSR account does not have
permissions.
What's going on? Shouldn't I be able to get to roles without having to know
the .aspx page? Where are the links for this?
I'm so confused. Thanks for any help.
RonNevermind. I needed to set anonymous access to off in both Reports and
ReportServer.
"Ronald S. Cook" <rcook@.westinis.com> wrote in message
news:%23oPNn$pWHHA.600@.TK2MSFTNGP05.phx.gbl...
> Yesterday, I was able to go to http://localhost/reports and manage roles
> and users in those roles.
> Today, that page looks different. I'm not sure if anyone ran anything or
> what, but I now just see links for various projects.
> I noticed in IIS that there is a pages/roles.aspx page so I typed
> http://localhost/reports/pages/roles.aspx and I did see the list of roles.
> But when I click on "Browsers" it tells me the IUSR account does not have
> permissions.
> What's going on? Shouldn't I be able to get to roles without having to
> know the .aspx page? Where are the links for this?
> I'm so confused. Thanks for any help.
> Ron
>
>
Subscribe to:
Posts (Atom)