Location to place favicon for report viewer / report manager - reporting-services

Where do I place a FAVICON.ICO file for SQL server reporting services 2008?
I can find information on the web for 2005 (IIS root and restart IIS) for 2008 R2 (ReportManager directory below RS install and restart service) and 2012 (same as 2008 R2?) but none of these seem to work for 2008.
To restate the question, if you are not using IIS where is the webroot on a server with SSRS 2008?

The favicon won't have anything to do with SSRS by itself, as long as it is in the website's root folder most browsers will automatically retrieve it. The only other way to add the favicon is through adding a <link> tag to the <head> portion of the web page but I do not believe you can modify the report manager website to that extent.
Make sure that you've placed the icon in the actual root of the entire website and not just the root folder of the report manager since it usually maps to http://reportserver/reports/ instead place it in the actual webroot which, as far as I know, the default for IIS is c:\inetpub\wwwroot\
Update:
I was unaware that SSRS 2008+ no longer required IIS. That is interesting.
From 2008 onwards SSRS uses http.sys to server HTTP requests so that it doesn't require IIS. This means that you are severely limited in the ways you can configure it. This forum post on MSDN Social seems to imply that you cannot put anything in the web root unless you have IIS. This this blog article gives a lot more information about http.sys and how it works.
MSDN does have a page about configuring the kernel mode driver http.sys and reserving url namespaces. But these all talk about forwarding the request to the SQL server anyway, so I'm not sure if it would be much help.
You could try changing the virtual directory that SSRS serves from to the webroot itself and place the favicon.ico file in the \Reporting Services\Report Manager\ folder but I'm not sure that will work and I can't test it at the moment.
Of course the easiest solution is to just install IIS and use it. Then it will be simple to add the favicon.ico to the proper location.

Related

SQL Server Reporting Services - cannot authenticate through URL on the same machine as SSRS server

I am accessing SSRS reports (SQL Server 2016) through URL to embed them in my application in an iFrame. When I access SSRS reports remotely, i.e from different computer I can authenticate and display the reports.
In my iFrame source I put:
http://example.com:4000/path_to_ReportServer/report_name
And that works fine when I deploy my app to stage server. All the SSRS reports load with no problem at all.
However I develop on the same PC as my SSRS report server resides, and when I am on it I have to change all the links in iFrames to:
http://computername:4000/path_to_ReportServer/report_name
edit: originally I wrote here that I use localhost, but actual I meant computer name.
If I try to run my app from VS on my dev machine and I do not change the domain to computer name I wont be able to authenticate at all. It just keeps asking me for the same credentials over and over again.
I've checked the ReportServerService log, and I see this as a last line when I try to log in:
library!DefaultDomain!3bd0!11/21/2016-12:52:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
I looked for this problem extensively, and I only find MS configuration tutorial but no one having similar issue to mine.
I have checked the usual culprits like firewall or port conflicts (but if I had any of those I would not be able to access the SSRS from any other PC, yet I can and the link doesn't work only on local machine.)
I am very new to SSRS in general so please kindly be patient with me. Thanks!
A few things you can try:
In SSRS Configuration and ensure that the Report Service and Report Management endpoints are valid (Copy the url in the hyperlink and make sure it opens on your local host.)
In SSRS Configuration and ensure that the Report Service Database has been properly deployed.
Remove any custom modules/assemblies you have applied to the default behavior from the ssrs web config (Custom Security).
I think you have applied changes to ssrs's web config in order to have it load assemblies for your custom security, custom datasourse/dataset, custom render format and fat fingered the config somehow.
You're probably running into a same-origin-policy error, which wikipedia states as under the policy, a web browser permits scripts contained in a first web page to access data in a second web page, but only if both web pages have the same origin.
The fix is to implement the X-Frame-Options metatag, like so:
X-Frame-Options: ALLOW-FROM https://example.com/

Install of Bolt CMS on Windows

I have installed the Bolt CMS on a Windows 2008 R2 server and it shows me a blank screen when I first try to launch it. I'm using IIS as the web server and MySQL as the database. I have verified that file permissions are set correctly for the folders that should be writable. PHP is also configured and working, and I have created my database and put the connection details into the config-yml-dist file. From my understanding the config.yml-dist file should be automatically renamed to config.yml when I run the application for the first time, but that isn't happening, in case that helps to know.
Can someone confirm if Bolt is compatible with Windows, and if so, provide any input on what I can check next?
Thanks.
I know a few websites with Bolt running on IIS / Windows 2008. If you're getting a blank screen, that means PHP is configured to not display errors. Which is the preferred setting for production servers, but not very convenient for development.
Either edit the php.ini file to 'display errors', or look in the server's error log for error messages. That should hopefully tell you what's going on.

Error: The specified TargetServerURL is not valid. Specify a valid URL for report server in the deployment settings

I have created a Report Server Project in Visual Studio 2013. The actual report server was a pre-existing server whose reports were previously populated via the Report Builder tool. I have downloaded the .RDL files locally and added them to the project under the /Reports folder.
When I try to deploy the reports I am receiving the 'TargetServerURL' is not valid error. I have researched the answers here and here.
I can successfully navigate to http:///Reports_PRODUCTION which displays the reports, and also to http:///ReportServer_PRODUCTION which offers an FTP-view of the report structure.
In the project properties I have set the 'TargetServerURL' to both of these URLs and neither has worked. I've verified that the target server version is correctly set - SQL Server 2008 R2. Am I missing something?
Thanks
I found out something, so that's why I post to this old question.
I had the same problems after starting a new VS2013 SSRS project and tried to deploy to the same RS server, but to a different server.
I kept getting the error: The specified TargetServerURL is not valid. Specify a valid URL for report server in the deployment settings.
After quadruple checking everything,I found that I was changing the ssrs project property on Release mode but in VS 2013 I was deploying the project in Debug mode. After changing the VS 2013 configuration to run as Release it found the right ssrs project settings and deployed fine on first run.
I read these answers and looked in my Configuration Manager (Right click project name > Properties > Configuration Manager > and picked the Server that was configured. It shows up checked like the image. I had been uploading with correct info, just didn't have the configuration fully done on my new project which used files and locations from older project:
Screenshot of Configuration Manager and Settings
I would start by looking at what SSRS thinks the service endpoint is and I bet that is the one you should be using.
Open the Sql Server 20XX Reporting Service Configuration Manager.
NOTE : This is found under the Sql Server progam group and maybe in a subfolder.
Select the service instance you want to connect to and click Connect
Navigate to the "Web Service Url" Tree List View Item in the list on the left hand side of the window.
Note the URLs: value in the "Report Server Web Service URLs" group box at the bottom of the Web Service URL panel. (This is the url you should use to connect with)
NOTE : If this is on a remote server then you will need to http or https to the domain in place of localhost or machine name if that is how the Report service was set up. If you can not access https:\\MACHINENAME/SSRS from your local machine then simply replace the url with https:\\www.mymachinenameurl.com/SSRS
make sure your deployment settings for the configuration you are deploying from are set (deploying in debug, ensure you are referring to debug deployment settings)
trust me I've been there .. Allot
I reached here because I've had the same error, and I was not able to deploy my report .
Anyways, at some point I tried to deploy the report manually by uploading to the library that I've already prepared with the Reporting Content Types, but the datasource was appearing as unknown file types, and couldn't access Manage Data Sources of the report.
tried to run the report hopelessly and noticed the url
http://ServerName/PWA/_layouts/15/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/PWA/Reports%20Library/Weekly%20Status%20Report.rdl
I tried to use the url http://ServerName/PWA/_layouts/15/ReportServer as "TargetServerURL" and it worked
for the other properties like the Datasets, reports ... I used the following urls
Report: http://ServerName/PWA/Reports%20Library/
DataSets: http://ServerName/PWA/Reports%20Library/Datasets
datasource: http://ServerName/PWA/Reports%20Library/datasource
and this was the end of my suffer and was able to deploy correctly and manage every property of the report, datasets, and datasources

Hosting basic html site on iis

I have a basic web site (just html, js and css files) that I want to host on IIS on my local machine for testing purposes. The site runs fine when I run it directly as a file on my computer. I added a website on IIS, using the directory these files are located in, but when I try to launch it, I get an error page that says:
An error occurred loading a configuration file: Failed to start monitoring changes to '[my site path]' because access is denied.
It then says that the source file is a web.config. I know that ASP.NET sites use a web.config, but I don't even have one, and I just want to run a basic site using html, css, and javascript.
Any ideas on what the fix might be? I made sure I have an application pool for the site.
You likely put it into your user profile -- ie c:\users\skitterm\ -- which won't let the process running IIS read the folder. You are better off using IIS' built in directory structure in c:\inetpub and adding a folder for your site.
As you can tell this is a server misconfiguration. It would help to know the version of your IIS.
You can follow the steps on Microsoft's official knowledgebase to resolve the issue:
http://support.microsoft.com/kb/316721
http://support.microsoft.com/kb/317955 (for IIS v6.0, try Method 3)
I worked in IIS about a year ago and such errors are caused by misconfigured Security settings in IIS.
Sounds like you need to set up the proper access rights for the folder to the account specified by the application pool identity.
First make sure that your folder is not anywhere under your \users\, \program files\, or any other place that already has restricted access. Put it under a folder on the root (\inetpub is a good place).
Then, add the appropriate permissions (usually read only) for the folder to allow the user account specified by the app pool identity to access it. If the app pool identity is set to ApplicationPoolIdentity, adding the IIS_IUSRS local group should do it. Otherwise, use the account that is specified.
This should fix the problem.

Using SSI (Server Side Includes)

I'm trying to learn how to do Server Side Includes because I need them for a project of mine. Now, can I use SSI locally? My site is 100% HTML, Javascript, and CSS, so there is no server running my stuff. I'm just editing the files in notepad. What can I do to allow me to work on SSI before I upload it to the server that I plan on sending it to.
What can I do to allow me to work on SSI before I upload it to the server...?
If you're not running a server, then you can't use server-side includes. The clue is in the name. So if you're testing the page locally without a server, then your SSIs won't work.
The only way you're going to be able to do this is to install a web server on your local PC.
Fortunately this is fairly easy. The two major web servers are Apache and IIS. Apache is free; you can download it and install it for free. IIS is a commercial product (by Microsoft), but there is a cut-down version you can install for free. Pick whichever one is best for you (ie the one which matches your actual web server), and you should be able to get your SSI code working. You'll probably need to do some config to set it up, but as a web developer that's a good thing to know how to do.
You need to run a server locally to make ssi work. You can install just apache, or use XAMPP (lite) to also get PHP and MySQL.
Server Side Includes (SSI) are an optional feature of the web servers helping the developers to include HTML file content from a base file into multiple other HTML files with a single line of code. We need this if we are creating a simple, elegant and fast pure HTML site, without active server computing, just invoking content delivery capabilities of the server.
There are 3 major steps required to get SSI running on IIS 7 and later:
Configure IIS roles,
Extend IIS handlers,
Invoke a SSI call in you HTML code.
HERE is a more detailed explanation.