Permissions problem - rsAccessDenied - Urgent

Hi

I'm trying to get the CustomSecurity sample in Reporting Services to work [C:\Program Files\Microsoft SQL Server\90\Samples\Reporting Services\Extension Samples\FormsAuthentication Sample\cs\FormsAuthentication] but I keep on getting the following message:

The permissions granted to user 'Admin' are insufficient for performing this operation. (rsAccessDenied)

I have given <servername>\ASPNET execute permissions.
I have successfully created a new user "Admin".

However, when I then try to logon to either ReportServer [http://miles/ReportServer/logon.aspx] or ReportManager [http://miles/Reports/pages/uilogon.aspx] I get the above error.

I'm using SQL 2005 Developer edition and XP professional.

Please help!

Connect to Reporting Services through Sql 2005

Select your reporting service project, right click and select Properties. In the Properties window select Permissions tab and add the group or user eg. <servername>\ASPNET and give all permissions to it. Say Ok

Permissions problem

Hi
I have some code that I am testing to read data from a FoxPro file.
I have copied the FoxPro file locally to test.
I have created a linked server that points to this file. Enterprise manager
correctly shows the tables available.
Works fine.!
However, when I create another linked server pointing towards the network
files, enterprise manager shows no available tables and my code returns an
error stating that the table does not exist.
I have checked the security permissions on the network drive/directories and
I appear to have full access. I can indeed move, delete etc these files.
Any ideas why I cannot connect in enterprise manager.?
ThanksI can however import these tables using a DTS job.!!!
"Chubbly Geezer" wrote:

> Hi
> I have some code that I am testing to read data from a FoxPro file.
> I have copied the FoxPro file locally to test.
> I have created a linked server that points to this file. Enterprise manag
er
> correctly shows the tables available.
> Works fine.!
> However, when I create another linked server pointing towards the network
> files, enterprise manager shows no available tables and my code returns an
> error stating that the table does not exist.
> I have checked the security permissions on the network drive/directories a
nd
> I appear to have full access. I can indeed move, delete etc these files.
> Any ideas why I cannot connect in enterprise manager.?
> Thanks|||Hi
Does the account that SQL Server and Agent run under have permission on the
remote share and files?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Chubbly Geezer" wrote:

> Hi
> I have some code that I am testing to read data from a FoxPro file.
> I have copied the FoxPro file locally to test.
> I have created a linked server that points to this file. Enterprise manag
er
> correctly shows the tables available.
> Works fine.!
> However, when I create another linked server pointing towards the network
> files, enterprise manager shows no available tables and my code returns an
> error stating that the table does not exist.
> I have checked the security permissions on the network drive/directories a
nd
> I appear to have full access. I can indeed move, delete etc these files.
> Any ideas why I cannot connect in enterprise manager.?
> Thanks|||Both services were running under local system. Have changed to my login but
still no joy.
Also in linked server security options I have tried changing them to login
as myself but no luck.
The following 2 lines of code ALSO return table data:
EXEC sp_tables_ex @.table_server='OPERA_SERVER'
EXEC sp_columns_ex @.table_server='OPERA_SERVER', @.table_name='ssale'
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Does the account that SQL Server and Agent run under have permission on th
e
> remote share and files?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Chubbly Geezer" wrote:
>|||Correction.
The following 2 lines of code DO NOT WORK..
EXEC sp_tables_ex @.table_server='OPERA_SERVER'
EXEC sp_columns_ex @.table_server='OPERA_SERVER', @.table_name='ssale'
"Chubbly Geezer" wrote:
> Both services were running under local system. Have changed to my login b
ut
> still no joy.
> Also in linked server security options I have tried changing them to login
> as myself but no luck.
> The following 2 lines of code ALSO return table data:
> EXEC sp_tables_ex @.table_server='OPERA_SERVER'
> EXEC sp_columns_ex @.table_server='OPERA_SERVER', @.table_name='ssale'
>
> "Mike Epprecht (SQL MVP)" wrote:
>sql

Permission for a role...

Hi
I have a server login Jans_Test.
This maps to a databaseuser Jans_Test in a database
In this database I have a schema AT. Default schema for Jans_Test is AT.
I also have a Database role db_dealer created in SQL with
CREATE ROLE db_dealer
GRANT EXECUTE TO db_dealer
User Jans_Test is member of role db_dealer. The role db_dealer is owned by
Jans_Test.
The role db_dealer owns schema AT.
All objects in the database is in the schema AT
I want to be able to add new users to the role db_dealer and then they
should only have permission to connect to the database and execute stored
procedures.
So the user should only have the permissions that is granted by the role.
And the role should only have permission to connect and execute stored
procedures.
How do I accomplish this?
Best regards
Jan Nielsen> User Jans_Test is member of role db_dealer. The role db_dealer is owned by
> Jans_Test.
> The role db_dealer owns schema AT.
Permission checking is bypassed for the object owner. Consequently, you
should not specify a role (db_dealer) as the schema owner if you want to
prevent members of that role from using objects in the schema.

> I want to be able to add new users to the role db_dealer and then they
> should only have permission to connect to the database and execute stored
> procedures.
> So the user should only have the permissions that is granted by the role.
> And the role should only have permission to connect and execute stored
> procedures.
The script below specifies a database user as the AT schema owner and grants
EXECUTE permission on the AT schema to db_dealer members:
EXEC sp_addrole 'db_dealer'
GO
CREATE USER db_dealer_owner WITHOUT LOGIN;
GO
CREATE SCHEMA AT AUTHORIZATION db_dealer_owner;
GO
CREATE USER Jans_Test FOR LOGIN Jans_Test
WITH DEFAULT_SCHEMA = AT;
GO
EXEC sp_addrolemember 'db_dealer', 'Jans_Test';
GO
--test security
CREATE PROC AT.usp_TestProc AS
SELECT OBJECT_NAME(@.@.PROCID)
GO
GRANT EXEC ON SCHEMA::AT TO db_dealer;
GO
EXECUTE AS USER = 'Jans_Test';
GO
EXEC AT.usp_TestProc;
GO
REVERT;
GO
Hope this helps.
Dan Guzman
SQL Server MVP
"Jan Nielsen" <jan_a_bilinfo.dk> wrote in message
news:uQXmJbA%23GHA.4468@.TK2MSFTNGP05.phx.gbl...
> Hi
> I have a server login Jans_Test.
> This maps to a databaseuser Jans_Test in a database
> In this database I have a schema AT. Default schema for Jans_Test is AT.
>
>
> I also have a Database role db_dealer created in SQL with
> CREATE ROLE db_dealer
> GRANT EXECUTE TO db_dealer
>
> User Jans_Test is member of role db_dealer. The role db_dealer is owned by
> Jans_Test.
> The role db_dealer owns schema AT.
>
> All objects in the database is in the schema AT
>
>
> I want to be able to add new users to the role db_dealer and then they
> should only have permission to connect to the database and execute stored
> procedures.
> So the user should only have the permissions that is granted by the role.
> And the role should only have permission to connect and execute stored
> procedures.
>
> How do I accomplish this?
>
> Best regards
>
> Jan Nielsen
>|||Hi Dan
Thanks a lot for answering. I'll look into this tomorrow.
Best regards
Jan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:718663FD-ED22-461D-97CF-81CC8A5283F6@.microsoft.com...
> Permission checking is bypassed for the object owner. Consequently, you
> should not specify a role (db_dealer) as the schema owner if you want to
> prevent members of that role from using objects in the schema.
>
> The script below specifies a database user as the AT schema owner and
> grants EXECUTE permission on the AT schema to db_dealer members:
>
> EXEC sp_addrole 'db_dealer'
> GO
> CREATE USER db_dealer_owner WITHOUT LOGIN;
> GO
> CREATE SCHEMA AT AUTHORIZATION db_dealer_owner;
> GO
> CREATE USER Jans_Test FOR LOGIN Jans_Test
> WITH DEFAULT_SCHEMA = AT;
> GO
> EXEC sp_addrolemember 'db_dealer', 'Jans_Test';
> GO
>
> --test security
> CREATE PROC AT.usp_TestProc AS
> SELECT OBJECT_NAME(@.@.PROCID)
> GO
> GRANT EXEC ON SCHEMA::AT TO db_dealer;
> GO
> EXECUTE AS USER = 'Jans_Test';
> GO
> EXEC AT.usp_TestProc;
> GO
> REVERT;
> GO
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Jan Nielsen" <jan_a_bilinfo.dk> wrote in message
> news:uQXmJbA%23GHA.4468@.TK2MSFTNGP05.phx.gbl...
>