Why a user needs to have access to the root to set properties of a subfolder < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Details:
A user can manage the content of a specific folder.
This user has no access to the home folder (the root).
Using the Report Manager, this user is able to browse the content of this folder directly (using ItemPath argument on the URL).
But when he selects Properties tab for this folder, he gets the rsAccessDenied error.
Giving him the right to browse the root corrects this problem.
Thank's
Eric
problem to set properties on a subfolder if no access to the home folder
TheSoddy
We decided that the most secure model for showing the contents of the report server was not to acknowledge the existance of a folder the user does not have access to. If that folder happens to be the root, then they cannot see it's contents.
Making a direct access to the folder succeeds because the user has permission.
Report Manager is not a programmatic interface - we do not support automating it in the way you describe. I don't know why it doesn't work, but it is not a goal of the interface to support direct access to items.
-Lukasz