Currently I am trying to work with reporting service instances through local network.
But the problem is, I am using WMI provider for getting reporting service instances from other machine in local network, I am getting access denied exception.
Do you guys have any ideas how can I actually return all reporting service instances in local network, maybe without using WMI if it is possible?
Thanks, looking for your advices.
You need to the have the local admin of the SSRS Server go in and add users to be a 'browser'. By default SSRS is set up with only the local admin who installed the SSRS Server instance as the only one able to view the site. You need to go onto that server, log in, go into the
'Reporting Service Configuration Manager', Should display your 'ReportServer' instance if properly set up. Click OK, Click the 'Report Manager URL' on the left side, go to the link displayed. The default is usually like 'http: //(servername)/Reports'.
Once in you typically click 'site settings' on the upper right in SQL 2008 and higher. Click Security, add user or group as a 'System User'. Next go back to the 'home' landing page. Click 'Folder Settings', Security do the same thing except for 'Browser' if you want them to see reports. If you cannot get to this main landing page from the local user that installed you have other issues and need to first determine that an admin can log on. This should be the first step of administering SSRS, is verifying the default admin can log in and see the site and the web service.
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.
I am using SQLServer 2008 Enterprise Edition running in Windows 7 Home Premium Edition, and I am having problems with the reporting service. The Reporting Service Configuration Manager does not show neither the Report Service Web Server Url nor the Report Manager URL. However, if I bring closer the mouse to the place where the aforementioned Urls should be a tooltip with the value of these addresses appears.
Using this invisible url I go to Report Manager and it is empty in spite of the fact that I have made an apparent successful deploy of some reports from my Visual Studio 2008.
In addition, when attempting to see the reports through the Report Service Web URL it gives me the following error :
"The permissions granted to user yamil PC yamil ' plow insufficient for performing this operation. ( rsAccessDenied ) "
At last, no one of the web sites related with Reporting Services appears in the Internet Information Services Configuration Manager. Is this normal?
This looks like permission or UAC error to me. By default, BUILTIN\Administrators or the local admin group on computer would have content manager role on RS. If you are already part of this group and you still see the error, You need to right click on your IE's icon and "Run as Administrator" before you try to browse the Report Server URL which throws the error.
For Report Manager URL, if its greyed out, URL reservation for Report Manager is not done. See if Apply button is enabled, If it is, Clicking on the Apply button under Report Manager tab should take care of it.
Make sure the user you are trying to login with is an administrator. Once that is done you should be able to go into the report manager url as specified in Reporting Services Configuration Manager.
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 have SQL Server 2008 on window server 2008 that is my report server.
My web application is in vs2010 which is on the other system. When I tried to show the report in report viewer it giving the following error:
The request failed with HTTP status 401: Unauthorized.
I used the ProcessingMode.Remote.
I want to use the database credential for accessing the report (please keep in mind that I don’t want to use windows credential).
I have set the following authentication in reportserver.config file.
<Authentication>
<AuthenticationTypes>
<RSWindowsNegotiate/>
<RSWindowsNTLM/>
</AuthenticationTypes>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
And on data source I have selected the “Credential stored securely in the report server” option.
More over when I use the window server 2003 report server its working fine and report viewer showing the report successfully, It create problem on window server 2008.
Please someone help me to overcome this problem. Is report server required some specific configuration for window server 2008?
Generally this occurs on the web server not keeping correct credentials to your data source. Start by going to the SSRS site: h ttp://(servername)/(Reports) by default.
There are a few questions you should ask:
Is this a report accessed by many so should I set up a domain account for it?
Or is this report only available to a few people and they should be prompted?
Generally you can go into the problem report. It will fail credentials. You can click it's hyperlink, click data sources on the left pane. You will see credentials set up. If you want to store them as you said you did, they should appear here under the radio button 'credentials stored in report server'. However many times an account should be listed here as a 'Windows account' or vice versa and is not.
I would also ensure once you get your data source down ensure your deployment settings are set to false for 'override data source'. Hope this helps.
I am having a problem with deploying the SSRS report onto the report server. When I try to deploy the report from visual studio, I get the following error:
The permissions granted to user 'krishna' are insufficient for performing this operation.
I am not sure where to give the permissions so that the report gets deployed and I can see my reports on the reports folder.
According to the article How to fix Reporting Services permissions are insufficient for performing operation (rsAccessDenied):
Make sure you have access configured to the URL http://localhost/reports using the SQL Reporting Services Configuration. To do this:
Open Reporting Services Configuration Manager -> then connect to the report server instance -> then click on Report Manager URL.
In the Report Manager URL page, click the Advanced button -> then in the Multiple Identities for Report Manager, click Add.
In the Add a Report Manager HTTP URL popup box, select Host Header and type in: localhost
Click OK to save your changes.
Now start/ run Internet Explorer using Run as Administrator.
NOTE: If you don't see the 'Site Settings' link in the top left corner while at http://localhost/reports it is probably because you aren't running IE as an Administrator or you haven't assigned your computer's 'domain\username' to the reporting services roles, see how to do this in the next few steps.
Then go to: http://localhost/reports (you may have to login with your Computer's username and password)
You should now be directed to the Home page of SQL Server Reporting Services here: http://localhost/Reports/Pages/Folder.aspx
From the Home page, click the Properties tab, then click New Role Assignment
In the Group or user name textbox, add the 'domain\username' which was in the error message
*(in my case, I added: DOUGDELL3-PC\DOUGDELL3 for the 'domain\username', in your case you can find the domain\username for your computer in the rsAccessDenied error message).
Now check all the checkboxes; Browser, Content Manager, My Reports, Publisher, Report Builder, and then click OK.
Your domain\username should now be assigned to the Roles that will give you access to deploy your reports to the Report Server. If you're using Visual Studio or SQL Server Business Intelligence Development Studio to deploy your reports to your local reports server, you should now be able to.
I encountered this same issue, but the resolution was different.
looking at http://localhost/Reports/Pages/Folder.aspx and I had to 'edit item security' to get the parent permissions to apply to the child folders and items (reports).
When I manually tried to upload using the "Upload File" function, it became clear.
(! Replacing an item with another one that has the same name, but is a different type, is not allowed.)
It seems the folders where the report is stored did not allow overwriting. I applied the parent folder permissions over the reports folder and we were able to deploy using Visual Studio again. Not sure how it got into this state.