I have a server that hosts nothing but reporting services. The default URL for the report manager is myserver/reports
Now, the server is only hosting SSRS and i would like the report manager to have the URL myserver/
How do i do that?
(the server 2012)
Thx
Nicolaj
Related
I have setup a SharePoint 2019 high-availability farm with 2 WFE's, 2 APP and 2 SQL Servers. All servers state is good and patched the farm with May 2022 Cumulative Update. We are running F5 load balancer and public IP of the load balancer (LB) is also added in the host file of both WFE servers.
We created a web application (its public facing site, so also added anonymous authentication) and added DNS to it. We have setup the AAM in central Admin and also added IIS binding for web application port and 443 (wildcard certificate is installed on both WFE servers).
When Load Balancer is pointed to WFE1, the application is loading perfectly fine, however when LB is pointed to WFE2, its showing a blank white page (with no JS or CSS loaded on the page, no errors). However, when we do IISRESET on WFE2, first time site loads on WFE2 and then goes blank if we refresh the browser or click on any link on the website. The application is working fine with server name on both the servers
We have tested on different browsers. Also added Disableloopbackcheck in Registry. All required firewall rules (ports) are open. Each server is getting pinged from one another, so there is no server communication issue. Even the required SharePoint files/folders are excluded from antivirus (Bitdefender). Also, there is no other web application on this farm which is using SSL/https.
I have also checked SharePoint ULS logs, Event Viewer logs and IIS logs, but it seems there are no errors.
Any help would be highly appreciated!
I'm trying to figure out how to host Team Foundation Server 2015 on the same IIS site as my SharePoint Server 2016. Currently, the SharePoint IIS site hosts my main SharePoint web application and a few other custom applications I've developed separate from SharePoint.
I want to use the same address and port for all of my applications (SharePoint, TFS, and custom) without using host headers. That is, http://www.example.com/sharepoint, http://www.example.com/custom, http://www.example.com/tfs.
I've managed to install TFS and move the /tfs IIS application it creates over to the SharePoint IIS site by modifying the applicationHost.config and changing some other settings. I'm prompted to login when I browse to http://www.example.com/tfs, but after I login I just get a blank page.
Does anyone know if this is even possible?
I have created an SSRS report using the Business Intelligence reporting service of VS 2012 and I have also successfully deployed it on the web service url i.e. http://computer name/ReportServer, the deployment was successful. The main purpose of deployment is to enable the client to access these reports from their machine, and I really do not have much idea on how to proceed with that, what and how do I give permissions to the client and how does the client access the above url in order to view the reports? Please elaborate I was not able to find much online help on this and its my first venture in this domain. Thank you very much in advance!
Open Reporting Services Configuration manager from windows Start
Connect to your Report Server
basically Two ULR tabs are available there
Web Service URL
Report Manger URL
you want to go to Web service URL
assign Some virtual Directory then use that URL for client PCs.
if not work use IP address in place on Computer Name
for credentials use Service Account Tab in this Manager
check Use another account
and what ever domain username is given here will be used for client to log in .
i Had same issue, i jst replaced computer name with deployed server IP address,
http://10.60.0.0/ReportServer
I've installed SQL 2012 in Sharepoint Integrated Mode and have Sharepoint 2010 installed on a different server. In Central Administration I have added a SQL Server Reporting Services Service Application and proxy. This all appears to have worked (the RS databases were created).
The problem is I cannot finish the configuration as I need the report server URL. Upon researching I found that this would be "http://myspserver/_vti_bin/reportserver" however this does not connect. I have looked at the rsreportserver.config file and where the URL should be is just
<ReportServerUrl>
</ReportServerUrl>
Upon looking at the at the service applications list I have noticed that the SQL Server Reporting Services Service Application is stopped. This might be why I can't connect to the URL so I tried stopping and restarting the SQL Server Reporting Services Service and although this was successful it made no difference to the state of the service application.
How to get this setup sorted out?
I've just installed Microsoft SQL Server Express 2008 (with Reporting Services).
My installation is side by side with SQL Server 2005.
So far creating reports and testing them in the development environment has worked fine, however I can't get the web server or report manager working.
In the Reporting Services Configuration Manager, it appears that they have been configured and have a working address (eg: http://mymachine:8080/ReportServer_EXPRESS2008/ and http://mymachine:8080/Reports_EXPRESS2008/).
The Virtual Directories don't exist in IIS, and clicking on the links in the config manager results in a "The page cannot be found".
If I create the Virtual Directories in IIS, and then use Reporting Services Configuration Manager to modify the two sites, Reporting Services Configuration Manager appears to be working correctly (all the right messages appear, indicating that it created the new site and dropped the old site successfully). However, it only drops the existing Virtual Directory and does not create a new one.
Has anyone had this problem before and/or know of a possible solution?
Basically, Reporting Services 2008 doesn't use IIS anymore.
By coincidence (or default?), I already had IIS (with Reporting Services 2005) running off port 8080. Reporting Services 2008 also wanted to run off port 8080.
It appears that the new IIS free address reservation system doesn't work in this situation. Changing the port number fixes the problem.