I have SSRS 2019 on one machine and data on another sql server 2019. On SSRS server website works fine and authentication as well.
When I go to the SSRS web site from my laptop I mostly see error.
and my identity is:
If I paste URL of existing working report, I prompted to fill user/password.
Then I can see report with data. But I'm still not properly logged.
ANONYMOUS LOGON
SSRS works like this most of the time. But sometimes after I enter credentials and refresh page, I'm logged as my user. But not always, sometimes there is still ANONYMOUS LOGON. It is the same on Chrome, Explorer and Edge.
SSRS configuration from config manager:
SSRS service account = Virtual Service Account SSRS database
conn to database authentication type = Current user - Integrated security Database
database credential authentication type = service credentials SQLServerReportingServices
My user has Browser, Content Manager, Publisher and Report builder role in Home/Manager Folder.
Reports have shared data source with Using windows name and password credentials. This windows account has read/write permissions on sql server with report data.
Connection string in form of:
Data Source=server01;Failover Partner=server02;Initial
Catalog=database;Integrated Security=True
My opinion is that this is authentication issue, but I cannot figure out where and how to fix it.
It is confusing that sometimes I'm authenticated and sometimes not.
Any ideas?
Related
I'm trying to set a report in Report Server (SQL Server 2017 Reporting Services 14.0.600.1669) that use the Windows credentials of the user who is viewing the report to query the datasource (SQL Server 2017 14.0.3430.2).
The report is deployed and works correctly if I choose to specify static WAuth credentials in the datasource (Test connection success):
If I choose to ask the user for Windows credentials it works fine too:
BUT when I choose to access the data source as the user viewing the report (ME, with the same WAuth) I'm reciving the error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
So it seems to not be using my user but another service account.
I've tried both with Microsoft Edge (IE 11 Compatibility Mode) and Chrome with the same result.
I'm not the person who have installed/configured this Report Server.
Can someone help me to find out what could be the problem/suggest what to check?
Thanks!
So, it seems it really was a double-hop authentication issue wich i managed to resolve with the help of IT. I don't know a lot about AD or Kerberos but this guide has been pretty helpful for me and IT to catch and resolve the missing configurations.
am getting the following error when attempting to run an MVC website in VS2013 and SQl Server 2014 using the ReportViewer control and accessing a report from the report server:
RSExecutionConnection MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.
I am using the correct report server url foun in the Reporting Services configuration manager. When I attempt to run the report in the SSRS project, the system prompts me for a user name and password. I enter the computer admin user/password. The report then runs. By the way, the reportviewer control uses the same user/password.
I am also able to access both the report server and reports urls in a browser with the same prompt for user//password.
I tried fiddling around with the report server role settings and under folder settings, this user has all privileges checked (browser, content manager, my reports, publisher, report builder).
Also as a side issue, I cannot see site settings even if I invoke the browser as an administrator.
I also looked in the SSRS Configuration manager. The service account is "Local System". The same admin user is listed in "Execution Account".
When running the website, I see no error entries in the SSRS log.
Please help, I have been looking into this for 2 days.
I think these solutions can help
Change from Local System to Network Service in Service Account of Reporting Services Configuration Manager
Update the web.config of ReportServer for these settings as below
<authentication mode="Windows" />
<identity impersonate="true" />
I'm using BIDS (Visual Studio 2008) to create and deploy SSRS reports to a report server, on a third-party hosted server.
The username and password that it uses to deploy reports onto the report server seems to be saved somehow, and I don't seem to be able to change it. Is there a way of changing this account? I'm getting a rsAccessDenied as expected. Previously it has asked for a username and password. To confirm, I'm getting this in the Error List pane:
The permissions granted to user 'SERVERNAME\ssrs' are
insufficient for performing this operation.
I can't start the software using these credentials as they only exist on the server. I can't change the permissions of this "fixed" account either as it's used by staff for read-only viewing of the reports. I already have an account for writing to the server that I would use if this software would let me.
I've looked at every setting I could find and I've tried creating a new solution, copying the report I need to deploy to this solution, but it still doesn't ask me for credentials.
The credentials were saved in Windows Control Panel -> Credential Manager (I'm on Windows 7). Just edit or delete the "Windows Credentials" for the server. For me, these credentials were, I think, saved by Internet Explorer rather than BIDS, but BIDS is happy to use them anyway.
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.
I get the following error when trying to run reports:
The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified. (rsInvalidDataSourceCredentialSetting)
By the way I am running it from VS2010 with SQL Server 2008 Reporting Services.
How do I solve this issue?
Yes, I've seen this. You can set the Credential and Connection Information such that a report is run impersonating the unattended user account. This article explains how to set up this type of report running. This setup is especially useful if you want to use the credentials inside a dynamic connection string (for example when you need to insert the credentials through a parameter).
If you don't want to run using the unattended user account, you should review your DataSource and connection string as defined in the report. Perhaps play around with the settings and different configurations for the datasource to create a different setup. The above links should be a start for some documentation.
In my case, it was because of some deployment parameters.
Go to Project Property by Right-clicking at the Project name in Solution Explorer and select Properties.
In Configuration Properties > General, change OverwriteDatasets and OverwriteDataSources in Deployment section to True for both parameters.
Click OK.
in my case, replacing linked server connections with local (fetched from remote locations and stored in local tables)data connections helped. we also checked this for ALL subreports/linked reports and it worked fine.
This happened to me today, it was because I was using the wrong datasource in my report. So I changed the datasource manually in Report manager and it worked. I guess another choice is to redeploy your report with the correct datasource.
This happened to me today. I am using Visual Studio 2019 for creating the reports for SQL Server 2014.
One of my reports had an embedded data source, but it was unconfigured/not configured properly. (You can see embedded data sources in the "Report data" pane under "data sources").
However, the embedded data source wasn't actually being used. I created the embedded data source earlier for debugging and forgot about it.
After deleting the unused embedded data source, the error went away.
This is from Microsoft:here
User Action
Change the settings for the current report so that it can run unattended, and then try to create the subscription or other scheduled operation again. Use the following steps to configure a report to run unattended:
1) Go to the Data Sources properties page of the report that you want to automate.
2) For the Connect Using option, select Credentials stored securely in the report server.
3) In User Name and Password, type credentials that can be used to access the database. If you are using SQL Server as the data source, the user name must be valid for both logging on to the server and for accessing the database that contains the data for the report.
4) If the user name and password are credentials for a Windows account, select Use as Windows Credentials. If the credentials are for a SQL Server user login, do not select this check box.
Do not select the check box Impersonate the authenticated user after a connection has been made to the data source, regardless of authentication type. This option cannot be used for reports that run unattended.