We are using ReportViewer 2015 in our ASP.NET Web application and using it with IE 11. When users (without admin permissions), try to print reports, they get the following error:
If i click, cancel on this error: then the following pop ups appear:
and then regardless we click yes or no, we get the following message:
Previously we were using Report Viewer 9 and this was all working fine but that version of Report Viewer does not render well in IE 11.
Also we are deploying RSClientPrint-x86.inf to all user's machine.
We have also temporary assigned users admin permissions to their machine and when the set up happens on their machine, we have copied the RSClientPrint assemblies and then distributed them but it does not work.
Also even once the assemblies are deployed, as soon as the admin permissions are taken away from the user, their printing stops working again.
Can anyone help?
First, to eliminate the obvious, have the user permissions been set correctly? Quick search yields a link
Second, reporting services use Windows authentication by default. Looks like you want to use forms authentication like so.
EDIT : So it looks like it is an Activex installation rights issue. For Activex installation without admin rights, on an admin command prompt type ocsetup.exe AxInstallService and enable it once done. You will have to configure it using GPMC. More details on that are here.
Related
I'm working on integrating a report into a browser, and I get this error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'dsFederatedSample_SurveyLevel_STG'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Does this have to do with SQL vs Windows authentication?
First thing I would try is to get a bit more information on the error - that's a pretty generic message.
You could enable remote errors as per the error message and replicate the error for more information.
Or check the Report Server error logs to see what error was logged.
%programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles\
The next step would be to connect as the Data Source user to the database, run any code/stored procedures that the report is using with the same parameters you're using when running the report, and see if any errors occur. Make sure the account you are using has permission and that you have entered the name and password correctly in the Data Source.
In SQL Server 2008 in addition to the above two options you have a third option to make this setting through SQL Server Management Studio.
1.Start Management Studio and connect to Report Server Instance (make sure you select 'Reporting Services' server type).
2.Right click on the ReportServer and Select Properties
3.Click Advanced
4.In EnableRemoteErrors, select True.
5.Click OK.
I had the same issue "Cannot create a connection to data source...Login failed for user.." on Windows 8.1, SQL Server 2014 Developer Edition and Visual Studio 2013 Pro. All solutions offered above by other Stackoverflow Community members did not work for me.
So, I did the next steps (running all Windows applications as Administrator):
VS2013 SSRS: I converted my Data Source to Shared Data Source (.rds) with Windows Authentication (Integrated Security) on the Right Pane "Solution Explorer".
Original (non-shared) Data Source (on the Left Pane "Report Data") got "Don't Use Credentials".
On the Project Properties, I set for "Deployment" "Overwrite DataSources" to "True" and redeployed the Project.
After that, I could run my report without further requirements to enter Credentials. All Shared DataSources were deployed in a separate Directory "DataSources".
In my case, this was due to using Integrated Windows Authentication in my data sources while developing reports locally, however once they made it to the report manager, the authentication was broke because the site wasn't properly passing along my credentials.
The simple fix is to hardcode a username/password into your datasource.
The harder fix is to properly impersonate/delegate your windows credentials through the report manager, to the underlying datasource.
The issue is because your data source is not setup properly, to do that please verify your data source connection, in order to do that first navigate to Report Service Configuration Manager through
clicking on the start -> Start All -> Microsoft SQL Server ->Configuration Tool -> “Report Service Configuration Manager”
The open Report Manager URL and then navigate to the Data Source folder, see in the picture below
Then Create a Data Source or configure the one that is already there by right click on your database source and select "Manage" as is shown below
Now on the properties tab, on your left menu, fill out the data source with your connection string and username and password, after that click on test connection, and if the connection was successful, then click "Apply"
Navigate to the folder that contains your report in this case "SurveyLevelReport"
And Finally set your Report to the Data Source that you set up previously, and click Apply
if you use null values in your stored procedure, you will need to set the parameters to accept null values. That worked for me.
In my case I had in one report many different datasets to DB and Analysis Services Cube. Looks like that datasets blocked each other and generated such error.
For me helped option "Use single transaction when processing the queries" in the CUBE datasource properties
I had a similar problem, and being the newbie that I am it took me a while to figure out but I learned the user must have a login in SSMS. I created the logins with the following parameters:
Under Server Roles - check sysadmin
Under User Mapping - I selected the database and the report server. For each I checked datareader and datawriter
Under Securables - I checked anything that would allow the user to connect to the database and view anything
I also found that one of the existing logins had denydatareader and denydatawriter checked. Once I removed these it worked.
I'm not saying this is the best way to do it, just what worked for me. Hope this helps
More information will be useful.
When I was faced with the same error message all I had to do was to correctly configure the credentials page of the DataSource(I am using Report Builder 3). if you chose the default, the report would work fine in Report Builder but would fail on the Report Server.
You may review more details of this fix here:
https://hodentekmsss.blogspot.com/2017/05/fix-for-rserroropeningconnection-in.html
I had the exact same issue.
The cause could be different but in my case, after trying several different things like changing the connection string on the Data Source setup, I found that this was the infamous 'double hop' issue (more info here).
To solve the problem, the following two options are available (as per one of the responses from the hyperlink):
Change the Report Server service to run under a domain user account, and register a SPN for the account.
Map Built-in accounts HTTP SPN to a Host SPN.
Using option 1, you need to select 'Windows' credentials instead of database credentials to overcome the double hop that happens while authentication.
After a fresh install of SQL Server 2012 Developer on my Windows 7 machine, I configure SSRS. Then, in IE (version 11), I try to access the SSRS server at http://(servername)/Reports. Windows asks for my username and password. Odd, because I'm an administrator. So I enter my username and password and I get this reply:
User '' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
Researching the issue, I come across a number of answers, including:
Reporting Services permissions on SQL Server R2 SSRS
SSRS 2008: User Does Not Have Required Permissions
The answers to these questions are similar:
Run IE as an administrator
Add the SSRS URL to Trusted Sites in Security tab of Internet Options
Retry SSRS URL
On success, add your user to Site Settings and Folder Settings with the appropriate permissions.
You should then be able to access SSRS without running IE as administrator
Additional workarounds include disabling UAC and repeating the steps above.
Running IE as an administrator did not work. At step 3. I got the same response as above and was never able to get to the SSRS home page.
Before disabling UAC, are there any other workarounds?
The workaround I found is from Peter O’Gorman's blog entry.
The steps above are the same, except add the URL to Local Intranet, not Trusted Sites:
Run IE as an administrator
Add the SSRS URL to Local Intranet in Security tab of Internet Options
Retry SSRS URL
On success, add your user to Site Settings and Folder Settings with the appropriate permissions.
You should then be able to access SSRS without running IE as administrator
To my pleasant surprise, this worked like a charm. Thanks Peter!
Run IE as an administrator - not Chrome. I swear I tried this before with no joy.
I don't understand why not Chrome and why administrator. Maybe Chrome somehow dismisses the elevated permissions. How does the rsManager know at what level the browser is running anyway?
Microsoft SQL Server Management Studio 12.0.2000.8
Microsoft Analysis Services Client Tools 12.0.2000.8
Microsoft Data Access Components (MDAC) 6.3.9600.16384
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 9.11.9600.17498
Microsoft .NET Framework 4.0.30319.34209
Operating System 6.3.9600
Chrome Version 39.0.2171.95 m
Same steps as Glenn mentioned previously. I also had to add user to role in two different spots once I was able to access SQL Server Reporting Services - Home. In Folder setting -> security -> new role assignment and site settings -> security -> new role assignment. I added my user as well.
http://techasp.blogspot.com/2013/06/how-to-fix-reporting-services.html
This works for Reporting Services 2008 onwards
This one has been bugging me for a while, some users have access to the report server others get this error message. While trying to resolve it with a system administrator I came across this post from microsoft support
For users to navigate to a particular folder, they must have Browser role on
all folders starting at the root folder (the folder named "/" in the
item path or "Home" in Report Manager). So you will need to grant
those permissions explicitly. By default, permissions are inherited
from the parent folder. If there are any breaks in the inheritance,
you will need to set those permission explicitly.
What we did as a administrator users, was to navigate to Reports page, then folder settings and grant the user that does not have permissions Browser rights to the folder. Use could then navigate to the home page and work their way down the tree. the sys admin hadn't granted access to the user at the home level just on the folders and reports that have access to.
I installed SQL Server 2008 R2 SP2 with advanced services on a Windows 8.1 environment. I selected the default configuration for the Reporting Service.
Everything seems to work, but when I try browse to the report manager I get the message
The permissions granted to user 'LocalMachine\User' are insufficient
for performing this operation. (rsAccessDenied)
The laptop is not part of a domain and the logged on user is the local admin. Does anyone have an idea how to overcome this issue?
Thanks in advance!
The problem you're encountering is due to UAC (user access control). Even though you're setup as an adminstrator you're account is not being treated as such unless you run IE as an Administrator.
To save having to remember this step each time, and to enable other browsers to be used and Visual Studio to deploy reports you need to setup your login as an explicit user to SSRS Server. Follow the steps below and that should do the trick.
Steps recommend using IE - other browsers can work with the following steps but not guaranteed.
Open Internet Explorer as Administrator(Right click the IE exe and
choose “Run as Administrator”
Go to the “SQL Server Reporting Services” Home page (http://localhost:port/Reports) which will redirect to http://localhost:port/Reports/Pages/Folder.aspx
Click on the “Folder Settings” button.
Click on the “New Role Assignment” button.
Add the Group or user name: DOMAIN\USER_NAME or in this case LOCALMACHINE\USER_NAME. You'll probably want to pick Content Manager role so your account has full functionality.
Hopefully the above will do the trick.
All, a peculiarity has shown up in SSRS. We have an ASP.NET 4.0 Web Application which interfaces with SSRS's ReportServer. Our reports are all developed in BIDS 2008. Normally, I build a report, manage my deployment configuration (in this case, 01 - Dev), and then deploy using the credentials provided by my server admin. No problem, right?
However, when I came in today to try and deploy changes to a report (so, not a new report), I made my changes, selected the report, and hit 'deploy.'
The normal login box never popped up to prompt me for my UN/PWD, and this error appeared:
"Error 1 The permissions granted to user '' are insufficient for performing this operation. 0 0"
Note that I have NOT removed my username from the above error - this is exactly how it appeared in BIDS. I checked with my server admin, and my deployment path, and all the options in the project's configuration seem to be correct, but the issue persists.
I've tried going online directly to the Report Server, and I can login just fine there and all my usual privileges seem to be in order.
I never even had a change to login.
Anyone have any ideas?
Sorry can't comment yet from low rep, but I've had this error before and it's on the SSRS server side because I have a custom report deployment tool and it has that error returned to the client. The solution is to play with the rights (remove and add some again) and it goes away. I have no idea what actually causes the problem.
Go to your report solution folder> Right click for properties > General Tab > remove 'Read only' check box. Then in the 'Security' tab, make sure all the permissions are allowed to the particular User role.
Hope it helps !
I am using SSRS 2012 for Reporting and when i deploy it on production server and try to access the report then it always prompt me for login and if we put the server login details then its working fine.
I want to avoid this login prompt and How can i do this, i did many search on Google and try do implement these but not get any luck.
Please help us.
Thanks
Atul
Check the IE's 'User authentication' settings (refer to screenshot in
http://blogs.msdn.com/b/axinthefield/archive/2011/05/06/logon-dialog-box-when-launching-a-reporting-services-report-from-ax.aspx)
Hope your issue is solved now. But I was looking to overcome same problem, and as I got a solution. I thought some other people might get help from this.
I was trying to deploy a report to our production server but it would prompt for user credentials again and again but wont deploy the report, and everything seemed to be alright with the report.
I tried every credentials being used on the server but nothing worked.
Eventually I had a thought that there are .RDL, .RDS files being used to generate report and somehow the same should be uploaded on the server and this time I used the FTP User account credentials and Bingo!, it worked.
Hope this saves time of other people.
IE Settings:
Open Internet Explorer
Go to Tools and click on Internet Options
Under the Security tab, click on Trusted sites and click the Sites button and Add Report Manager/Report Server URL to the trusted
sites.
Then click Custom Level, and check the option Automatic logon with current user name and password
Repeat #3 and #4 for Local Intranet
Taken from: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b1efd3f0-4fc5-4015-b13a-b79737466271/how-to-stop-prompting-for-username-password-when-i-click-report-server-web-service-urls-in-ssrs?forum=sqlreportingservices
Login into "Server"/ReportServer
Click on rdl file "drop down"
Select Manage
check if the Data Source's Connection String box is empty
If it's empty, provide the Connection String again
Select the Option Windows Integrated Security
Test and save your Connection String.
This will overwrite your localhost credentials.