SSRS on MSSQLServer 2008R2 with Report Builder 3.0 I Created RDL report in RB3.0. The Data Source is a view in a database in MSSQLServer running on the same box. My login is part of the administrators group on the domain as well as on the local computer. There is no Report Service web site or virtual directory in Local IIS Through the Report Manager URL .Site Settings.Security the BUILTIN\Administrators group has System Administrator, System User permissions. In Folder Settings the BUILTIN\Administrators group has Browser, Content Manager, My Reports, Publisher, Report Builder The following is the full error message. System.Web.Services.Protocols.SoapException: The permissions granted to user 'DOMAIN\rob' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'DOMAIN\rob' are insufficient for performing this operation. at Microsoft.ReportingServices.WebServer.ReportingService2010Impl.CreateReportEditSession(String Report, String Parent, Byte[] Definition, String& EditSessionID, Warning[]& Warnings) at Microsoft.ReportingServices.WebServer.ReportingService2010.CreateReportEditSession(String Report, String Parent, Byte[] Definition, String& EditSessionID, Warning[]& Warnings) ---------------------------- The permissions granted to user 'DOMAIN\rob' are insufficient for performing this operation.

Hi RobGMiller, In Reporting Services, the Execute Report Definitions task indicates we can start execution from report definition without publishing it to Report Server. In your case, I suggest you to verify required tasks are in the role definitions. Please refer to the following steps to verify the permission: 1. Start Management Studio and connect to the report server. 2. Open the Security folder. 3. Open the System Roles folder. 4. Right-click System Administrator, and select Properties. 5. Select Execute report definitions and click OK. 6. Right-click System User, and select Properties. 7. Select Execute report definitions and click OK. For more information about Configuring Report Builder Access, please see: http://technet.microsoft.com/en-us/library/ms365173(v=sql.105).aspx Regards, Bin Long TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Bin Long TechNet Community Support

Thanks for your reply Bin, Unfortunately your instructions do not reflect my environment or are not detailed enough. I start Microsoft SQL Sserver Management Studio. Connect to the local database which, in this cases, manages the ReportServer database There is a security folder in the first level (same level as the Databases folder) but it does not contain a System Roles folder. It contains a Server Roles folder and it does not contain a System Administrator listing. The ReportServer Database has a Security Folder but it does not contain a System Roles folder either. It contains a Roles folder and it does not contain a System Administrator listing. SQL Sever is version 10.50.1617. I am loggin in as "SA" perhaps I need a different login.

Thanks for clarifying. I have found System Administrator in System Roles as described in your first reply. Right Click finds the Properties of the System Administrator greyed out / disabled. If I use F4 it opens the properties window but it is empty. My login is in the Administrators group of this computer and the domain used to login. I was logged in using this same login when SQL Server 2008 R2 was installed. I appears I do not have enough rights to make the suggested change. I cannot delete a Role or a system role of view their properties or content. The other day, I used the Report Manager URL available from the Reporting Services Configuration Manager to change the System Administrator roles. Now the Settings link at the top left of that screen is not displayed. I'm sure I added all the available roles to the, I believe, System Administrator account.

Hello, Please right-click on SQL Server Management Studio and select Run as administrator, and then connect to a Report Server instance. For more information, please see: Is it possible to edit or add new role in SSMS for report server: http://social.technet.microsoft.com/Forums/is/sqlreportingservices/thread/b68b9bba-b46a-4eb3-80a5-62808adc31ca SSRS Properties greyed out in SSMS on Windows 2008: http://social.technet.microsoft.com/forums/en-US/sqlreportingservices/thread/412df0eb-bc5f-4dd9-b637-e23a4d127e1c Furthermore, it seems that Site Settings option is missing on the Report Manager. In Reporting Services, the Site Settings option only available for System Administrator role on the Report Manager. In your case, I suggest you right-click on the Internet Explorer and select Run as administrator. Regards, Bin LongBin Long TechNet Community Support

Hi Bin, After setting up the system administrator as you suggested I am back in Report Builder 3.0 and looking at my report. I setup the Data Source to connect to the Local SQL Server 2008R2. After entering the sa User Id and password the connection test is successful. However, when I run the report, I get the following error set: Logon failure: unknown user name or bad password ---------------------------- Log on failed. Ensure the user name and password are correct. (rsLogonFailed) ---------------------------- The report server has encountered a configuration error. Logon failed for the unattended execution account. (rsServerConfigurationError) It behaves like the user name and password has to be embedded in the report as opposed to being imbedded in the Data Source configuration.

Hello, Based on the error message, it seems that you configured an unattended account for Reporting Services and the password has expired. Please refer to the following article to reset the account and password: Configuring the Unattended Execution Account: http://technet.microsoft.com/en-us/library/ms156302(v=sql.105).aspx Thanks, Bin LongBin Long TechNet Community Support

Thanks again Bin, Still doesn't work. In addition, the Data Source that was connecting yesterday is not longer connecting today. However, I created a new shared datasource accessible by the ReportServer and it seems to connect. The article you referred me to suggests that there can be one unattended account that can be used to connect to resourses that require authentication that is configured in a report server service. I used an account that can view and modify data on the SQLServer database used as a data provider for the Data Source of the report. In the Data Source Properties.General screen I used a Shared connection. The fields in the credentials screen are disabled. If I connect the dataset to this data source and run a query, I don't have to use credentials and data is returned. Still when I run the report I get the same original error message that indicates that my current login is unable to do something. Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'Domain\Login' are insufficient for performing this operation. I can see no place, other than the Data Source, where the current login is or can be specified as the method to connect to either the Data provider database or the ReportServices session or database. The kicker is that my current login has full access to absolutely everything on this computer. So even if it was using the current login to access resources, it should be able to.

Hi Bin, I've been working with a MS support specialist to help resolve this issue. It turns out that the error messages I'm getting are not very representative of what the errors are. We removed a code segment in an included Espression that refers to Globals!TotalPages and that made the report run without an error. Another thing we found is that no report runs without the above error message unless Report Builder 3.0 is run as Administrator. I was wondering if this is a normal condition and if not what kinds or confirguration might have an effect on it. Might it be the Database that contains the data or the database the contains the report server data or the report server service itself. I am concerned that when these reports are called from an ASP page they might have the same problem.

In response to: "I am concerned that when these reports are called from an ASP page they might have the same problem." I ran into the same problem but discovered the error was the result of "using a shared connection or report model" on Report Builder 3.0 (RB3) and on the SSRS side it is called "used shared data source reference"; even though both SSRS and RB3 call see and load the same ".rdl file. RB3 is looking for a newer version ".rsds" or ".smdl" which is not exactly what SSRS is using ".rds" i.e. \Documents\Visual Studio 2008\Projects\SSAS Cube 1\SSAS Cube 1 v2\SSASCube v1.rds By the way a shared dataset is a .rsd. By removing the shared connection and going to the connection embedded in report option fixed it for me. However, that means you cannot use the 'shared connection' between SSRS and RB3 option; if you plan to use RB3, in my opinion, without converting all SSRS "shared connection" - ".rds" into a ".rsds" and placing them in the same location - which RB3 can find or have access rights. It is assumed 'shared connection' are meant only for SSRS report development and if possible RB3 has its own set of 'shared connection'. If my comments are of any help to anyone then this reply posting was worth it. What drew me to this web page was that I encountered the same or also the same error message - it looks like the same error message and my issue was between RB3 and SSRS ".rdl file sharing. Meaning you could create or modify an ".rdl file in SSRS and RB3 could also modify or add to it and so on. I believe the thinking was Model Projects would feed RB3 users once SSRS deployed it to them and 'let them run with it'; and that works just fine for 'shared connection'. i.e. ____http://hp/ReportServer_RANCH/models This does not directly touch on this last concern of ASP page problems - but I am hoping it may also resolve that concern as well. +---------------------------------------------------------------- Now when you create and deploy from SSRS the following to ____http://hp/ReportServer_RANCH: Shared Data Sources --> Northwind_Shared.rds Shared Datasets --> Northwind_Shared.rsd Reports --> Report1.rdl to RB3 everything works just fine when RB3 goes over and gets Report1.rdl from: ____http://hp/ReportServer_RANCH/Report1Project1/ because Northwind_Shared.rsds is there at ____http://hp/ReportServer_RANCH/Data Sources and because Northwind_Shared.rsd is there at ____http://hp/ReportServer_RANCH/DataSets +---------------------------------------------------------------- __ __ A little more on the 'shared connection' issue would reflect this from MS; if you want more info on how RB3 leaned toward SharePoints view verse staying with SQL2008R2, in my opinion. http://technet.microsoft.com/en-us/library/bb283152.aspx Quote from above technet ' An .rsds file is similar to an .rds file, but it has a different schema. To create an .rsds file, you can publish an .rds from Report Designer or Model Designer to a SharePoint library (a new .rsds file is created from the original .rds file). Or, you can create a new file in a library on a SharePoint Site. '

SSRS on MSSQLServer 2008R2 with Report Builder 3.0 In response to "I am concerned that when these reports are called from an ASP page they might have the same problem." I ran into the same problem but discovered the error was the result of "using a shared connection or report model" on Report Builder 3.0 (RB3) and on the SSRS side it is called "used shared data source reference"; even though both SSRS and RB3 call see and load the same ".rdl' file. RB3 is looking for a newer version ".rsds" or ".smdl" which is not exactly what SSRS is using ".rds" i.e. \Documents\Visual Studio 2008\Projects\SSAS Cube 1\SSAS Cube 1 v2\SSASCube v1.rds By the way a shared dataset is a .rsd. By removing the shared connection and going to the connection embedded in report option fixed it for me. However, that means you cannot use the 'shared connection' between SSRS and RB3 option; if you plan to use RB3, in my opinion, without converting all SSRS "shared connection" - ".rds" into a ".rsds" and placing them in the same location - which RB3 can find or have access rights. It is assumed 'shared connection' are meant only for SSRS report development and if possible RB3 has its own set of 'shared connection'. If my comments are of any help to anyone then this reply posting was worth it. What drew me to this web page was that I encountered the same or also the same error message - it looks like the same error message and my issue was between RB3 and SSRS ".rdl' file sharing. Meaning you could create or modify an ".rdl' file in SSRS and RB3 could also modify or add to it and so on. I believe the thinking was Model Projects would feed RB3 users once SSRS deployed it to them and 'let them run with it'; and that works just fine for 'shared connection'. i.e. ____http://hp/ReportServer_RANCH/models This does not directly touch on this last concern of ASP page problems - but I am hoping it may also resolve that concern as well. +---------------------------------------------------------------- Now when you create and deploy from SSRS the following to ____http://hp/ReportServer_RANCH: Shared Data Sources --> Northwind_Shared.rds Shared Datasets --> Northwind_Shared.rsd Reports --> Report1.rdl to RB3 everything works just fine when RB3 goes over and gets Report1.rdl from: ____http://hp/ReportServer_RANCH/Report1Project1/ because Northwind_Shared.rsds is there at ____http://hp/ReportServer_RANCH/Data Sources and because Northwind_Shared.rsd is there at ____http://hp/ReportServer_RANCH/DataSets +---------------------------------------------------------------- __ __ A little more on the 'shared connection' issue would reflect this from MS; if you want more info on how RB3 leaned toward SharePoints view verse staying with SQL2008R2, in my opinion. http://technet.microsoft.com/en-us/library/bb283152.aspx Quote from above technet ' An .rsds file is similar to an .rds file, but it has a different schema. To create an .rsds file, you can publish an .rds from Report Designer or Model Designer to a SharePoint library (a new .rsds file is created from the original .rds file). Or, you can create a new file in a library on a SharePoint Site. '