I have installed RS in development with no problems, but after installing on
a production server, I can not see the Content tab on the home page and can
not create folders. DBA's are not allowed to be administrators on
production servers. I went into site settings and created a new role
assignment making myself a systems administrator in report services but still
cannot see the content tab.Did you solve this ? I have the same issue and have been battling for
days!!!
"Andy998" <Andy998@.discussions.microsoft.com> wrote in message
news:8F4AC6DF-4AA1-4BBD-9AA3-C1C6078BAFEC@.microsoft.com...
> I have installed RS in development with no problems, but after installing
on
> a production server, I can not see the Content tab on the home page and
can
> not create folders. DBA's are not allowed to be administrators on
> production servers. I went into site settings and created a new role
> assignment making myself a systems administrator in report services but
still
> cannot see the content tab.
Showing posts with label properties. Show all posts
Showing posts with label properties. Show all posts
Monday, March 12, 2012
Permissions can't see the contents or properties tabs on the HOME
Labels:
cant,
content,
contents,
database,
home,
installed,
installing,
microsoft,
mysql,
oracle,
page,
permissions,
production,
properties,
server,
sql,
tab,
tabs
Wednesday, March 7, 2012
permission window
Running sql server 2005 standard edition (SP1).
Server properties, permissions window seems to be different to what it
should be.
In this window I do not see System Administrator and System User column. I
see a different window i.e. permission, Grantor, Grant, WithGrant, Deny
columns.
Any thoughts please?
Thanksfarshad (farshad@.discussions.microsoft.com) writes:
> Running sql server 2005 standard edition (SP1).
> Server properties, permissions window seems to be different to what it
> should be.
> In this window I do not see System Administrator and System User column. I
> see a different window i.e. permission, Grantor, Grant, WithGrant, Deny
> columns.
> Any thoughts please?
Not really sure what you expect to see, but what you see is the server-level
permissions for a user, from whom he got it, and whether the permission
was granted or denied.
Keep in mind that the permissions structure has changed radically in SQL
2005, and is now far more complex than before. At the same time it's easier
to use, since you can grant a permission like EXEC on a schema, and it will
be inherited to procedure level.
There are some functions to display permissions: fn_my_permissions
and has_perms_by_name, and you can also query the catalog views directly.
But I have a feeling that more is needed.
The permissions dialogs in Mgmt Studio does a very poor job to show you
what the current permissions are. This particlar dialog you found is one
of the better.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Server properties, permissions window seems to be different to what it
should be.
In this window I do not see System Administrator and System User column. I
see a different window i.e. permission, Grantor, Grant, WithGrant, Deny
columns.
Any thoughts please?
Thanksfarshad (farshad@.discussions.microsoft.com) writes:
> Running sql server 2005 standard edition (SP1).
> Server properties, permissions window seems to be different to what it
> should be.
> In this window I do not see System Administrator and System User column. I
> see a different window i.e. permission, Grantor, Grant, WithGrant, Deny
> columns.
> Any thoughts please?
Not really sure what you expect to see, but what you see is the server-level
permissions for a user, from whom he got it, and whether the permission
was granted or denied.
Keep in mind that the permissions structure has changed radically in SQL
2005, and is now far more complex than before. At the same time it's easier
to use, since you can grant a permission like EXEC on a schema, and it will
be inherited to procedure level.
There are some functions to display permissions: fn_my_permissions
and has_perms_by_name, and you can also query the catalog views directly.
But I have a feeling that more is needed.
The permissions dialogs in Mgmt Studio does a very poor job to show you
what the current permissions are. This particlar dialog you found is one
of the better.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Labels:
database,
edition,
itshould,
microsoft,
mysql,
oracle,
permission,
permissions,
properties,
running,
server,
sp1,
sql,
standard,
window
Subscribe to:
Posts (Atom)