I have a server running SSRS. Visiting the server URL directs to the intranet URL:
http://server/CloudReports/Pages/Folder.aspx
I believe the 'CloudReports' folder name was customised previously but where can I edit this?
I've looked in Reporting Services Configuration Manager and can't find anything.
Related
We're using SSRS 2016 & SQL SERVER 2016 in our environment and don't want to use IIS. We've a requirement to re-direct report manager URL to Target URL (Similar to URL rewrite function of IIS).
For example:
http://ssrs01/pages/redirect.aspx?redirectnewurl
When someone access above URL they should be automatically routed to - "redirectnewurl"
I did research a lot and found this link useful which redirects from http: to https:
https://www.experts-exchange.com/questions/26319133/SSRS-2008-R2-How-to-redirect-URL-from-http-to-https-when-IIS-not-installed.html
But we don't have any need to use SSL as it is only internal environment and looking for any other optimal solution by changing web.config file in my reporting server
We have hundreds of SSRS 2005 reports in an ASP.Net 2.0 application. We are using following Javascript for rendering the report
window.location.href = url;
Url Example
http://aaa88/ReportServer/Pages/ReportViewer.aspx?/InventoryTracking/Receiving/MyReport&rs:Command=Render&rc:Parameters=false&Emp="20"
Example: Generate report from URL - SQL Server Reporting Services 2008
By typing the url anybody in the domain is able to view the report.
We need to ensure that the report should not be accessible without entering proper credentials.
We must also ensure that the website is able to render the report using "window.location.href" and without prompting the user
What is the solution for this in SSRS 2005?
I configured SSRS 2008 on a remote server.
I can access the report manager from my local machine using http://SERVER_NAME/Reports_INSTANCE_NAME
problem is that when I try to deploy a report from BIDS, I get the "reporting services login" dialog box that asks me for user and password. I try my AD user and it doesnt work.
I already added myself to all possible roles, including System Administrator.
I saw online that the problem maybe with the IIS website that must be configured to allow anonymous access. That's fine, but where can I configure that since SSRS2008 doesn't create the websites on IIS anymore (also read that online) and I don't seem to have this possibility using the Reports Service Configuration Manager
Take a look at the link below...it's in reference to 2008 CTP, but there are still some items to check in your setup...
http://blogs.msdn.com/b/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx
Similar issue / resolution here as well...
Repeated Reporting Services Login issue when deploying through BIDS to a remote server
In your report configuration file, try removing the RSWIndowsNegotiate from the Authentication tag:
<Authentication>
<AuthenticationTypes>
<RSWindowsNegotiate />
</AuthenticationTypes>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
I use a Apache server as frontend balancer. So I also pass requests to a SQL Server Report Server.
The main URL is SSL secured, so the ProxyPass through the RS works with basic auth.
The report server has a interesting issue. Most of the links in the report server seems to be hardcoded http://. With that issue, many links you click on the /reports URL gives you a "Bad Request (Invalid Hostname)" from the Apache front end server.
You can browse reports, you can open them, but if you click e.g. the root link on top or the view details link to switch the list mode, then the report server uses http://yourserver/reports/... which results in an error. Correct links are https:// in this setup.
Link which are not http:// hardcoded works so far.
I opened a support ticket at Microsoft already which escalated to redmond to the dev team. The result was... this is by design and can't be changed. Is MS really so censored? Anyway. Did anyone face the same situation and got a workaround to fix that?
I am not that familiar with Apache config, but maybe is there a way to do a URL rewrite within the Apache? So if the Apache gets an http://myfrontendurl/reports/... it replaces the request with https:// ?
I'd recommend deactivating the http access from the Reporting Services Configuration tool and seeing what happens.
I am trying to install and configure SSRS on SQL 2005.
When I click Reporting Services Configuration, I get a message saying
No report servers were found on the specified machine - Details
Invalid namespace.
How can I resolve this?
You don't "configure SSRS on SQL Server 2005", as such.
It's a component that you choose at install time (like Analysis Services, Integration Services etc). For SSRS, then you require IIS as a prerequsite and it won't be installed if IIS is not present.
The error itself is 100% correct if SSRS is not installed...
Is it actually installed?
Edit:
Just got this on one of my feeds: KB 960374 that describes the exact error above
Quite simple. Place your disc with SQL in and run setup. Add features to your existing instance and select Reporting Services. Once installed it would have created 2 databases on your SQL Server named ReportServer and ReportServerTempDB
Open the services configuration and you should be prompted to connect to an instance of Reporting Services.
If you see this screen then you are ready to go.
--Read this only if you might have questions to ask
Setup a service account for Network Service (save the .snk key and it will create your IIS entries etc. If you don't have IIS then upgrade your OS to a compatible version. It can be installed via Add or Remove Windows Features)
Make sure your new database is selected in the Database section. If not, then follow the screen to add it
Open the Report Manager URL and click on the link. (You may need to be in as an administrator)
When you want to deploy reports, simply update your solution properties with the TargetURL pointing to the Web Service URL that is available after setting up the Service Account)
Ask anything further if you need the guidance. I've done this to about 5 servers in the past month already, so I know what can go wrong.
Cheers,