I recently installed SSRS 2016 on a Windows 2012 R2 machine and when I go to the Report manager URL I get a blank page. I used the defaults when configuring SSRS except I changed the port from 80 to 8080. The version of SQL Server that SSRS is using is 2016 SP1 and is located on the same server. I'm a local admin on the box. SSRS is installed on the default instance (there is a 2012 and 2014 SQL Server named instance on the box as well but no other installation of SSRS).
The blank page doesn't leave me much to go on in regards to figuring out what the issue is. I've come across a few other posts where people have reported similar issues with the usual cause being changes to virtual directories or insufficient permissions. I don't think that's the issue here but a blank screen doesn't tell me much either way.
Any suggestions on what would cause of a blank page for Report Mgr or suggestions on how to trouble shoot would be greatly appreciated.
By default, the Internet Explorer Enhanced Security Configuration is enabled on the server. This causes the ReportManager site to be entirely blank. If I look at the Page Source in IE Developer Console, all HTML is shown.
Went to Server Manager -> Local Server -> IE Enhanced Security Configuration and turned it off. Report Pages are now displayed as expected.
Try to put your URL in the trusted sites in Internet options
Related
I set up an office web apps server 2013 in windows server 2012 R2, it is good to open this link http://localhost/hosting/discovery, means the office web apss server 2013 is running well.
But when I tried to open this link http://localhost/op/generate.aspx, it gives an error : A big red X, server error sorry for the mistake. We have recorded an error for the server administrator.
I was looking for some blogs, somesay that is causing by logging in the website with the system account, but I dont know what is the system account, and is that logging means the iis service?
I am not use WOPI and sharepoint, what I want is only use office web apps server 2013 to provide view & edit doc and docx files in browser.
Please help, thanks!
PS. If the question not meet the requirement, comment it, I will edit it.
eidt 1 :
I had solve this problem, I had installed AD and OWA in one server.
Install them in different server will ok.
But there is another problem :
When open a word file, It gave an alert:
Microsoft Word Web App
sorry, some problem had appeared, cant open this file.
How to fix this ...
update :
I finally solved it by changing another server to install OWA.
If you want to be able to open documents from UNC paths then run the following command in the PowerShell on your OOS/OWA machine.
Set-OfficeWebAppsFarm -OpenFromURLEnabled
If you need to connect your OOS/OWA to a WOPI host (SharePoint or a custom host) then http://localhost/hosting/discovery is a good enough indication that the instance works fine.
As described in the title, the app simply stops working after some time.
The application itself is a simple, one page form that pulls data from a webapi on another webserver by use of the Sharepoint WebProxy and displays that data using knockout.js. The environment and the Sharepoint Server (On-Premise, same domain as my Dev Machine) are configured correctly - supposedly - as described in
Configure an environment for apps for SharePoint (SharePoint 2013)
I can develop, debug in VS, deploy and open the App directly on the Sharepoint Site.
But after a while, when opening the app again without having changed or redeployed anything it stops at this point in the redirect process:
https://sharepointurl/_layouts/15/appredirect.aspx?instance_id=<some-guid>
and shows the "This page cannot be displayed" message. The Sharepoint Site still works.
There are no errors in the eventlog. Most of the time I can fix this by restarting the IIS service completely on which the Sharepoint Site resides. But sometimes even that doesnt work.
What could be the problem? Any Idea?
Update: The error is not consistent in that it may occur for user A but not for user B and even that can exchange after some time, so that the user B sees the error and user A can use the App.
Update: The error only occurs in IE 11 and doesn't happen when using Google Chrome.
Update: It seems as if Sharepoint 2013 Apps do not work with Internet Explorer 11, which I was using. As we had other issues with IE 11 and Reporting I downgraded my development machine to IE 10 and now it works.
Update: This had nothing to do with IE 11 either. The error eventually returned.
My first recommendation would be to have your client use the 32-bit version of Internet Explorer, even on a Windows 7 64-bit Operating System. Internet Explorer is the ideal browser for Active X and the preferred browser for SharePoint Online for Office 365.
Next I would recommend that your client configure Internet Explorer for SharePoint Online, to review the article detailing this process click here.
My last recommendation would be to have them install the latest updates and configure their computers for use with Office 365. The following links and instructions will detail that process.
I am trying to install IIS on my Windows 8.1 laptop and followed the directions at Microsoft for installing IIS. But when I type localhost, instead of getting the IIS start page, I get a blank page.
When I do Windows + R and type services.msc, the resulting list of services is long but does not include Internet Information Services.
When I look at the Windows filesystem, I do find the inetpub folder with four subfolders, including wwwroot. In the wwwroot folder is the iisstart.htm file that is supposed to display when I type localhost into my browser.
I have read that one possible problem is that both Skype and IIS want to use Port 80 and there is a conflict. So I decided to try to change the default port for IIS, but I found that I don't appear to have the IIS Manager on my system. When I go to Administrative Tools, Internet Information Services Manager is not on the list of administrative tools.
I added both the HTTP Redirection module as well as the IIS Management Service on top of the initial basic installation that Microsoft described. Still no luck getting IIS working or IIS Manager to appear.
I have tried to research this problem of getting IIS to work on Windows 8.1 with no success and am at a loss. Suggestions welcome!
In Control Panel --> Programs --> Programs And Features --> Turn Windows features on or off -> Internet Information Services -> World Wide Web Services -> Common HTTP Features -> Static Content.
Also make sure .NET Extensibility 3.5 and .NET Extensibility 4.5 are checked.
Major fail by Microsoft. Why the hell would they turn off the most basic features by default. Go to Turn Windows features on or off (just search "features"). Look in IIS, WWW, Common HTTP Features. See attached image.screenshot
I have solved a couple of my problems.
I installed several more IIS modules: Static Content, IIS Management Console, and HTTP Errors.
I am now am able to find the IIS Manager in the Administrative Tools list and can use the IIS Manager.
Also, when I pressed Windows key + R and typed in services.msc, I still don't see Internet Information Services in the list. However, I do see "World Wide Web Publishing Service" in the list and it is shown as running. A page at Microsoft's Technet site indicates that it is related to IIS.
The HTTP Errors module gave me an error page rather than a blank page when I typed in localhost and also when I typed localhost/filename. This proved a HUGE help, because the error page identified the problem as a permissions issue. I thought I had dealt with the permissions issues, but this error page made it apparent that I had not.
When I typed in localhost, I got the permissions error. When I typed in localhost/iisstart.htm, I got the proper display of the file. When I created a simple .htm file, statictest.htm, and placed it in the wwwroot folder along with iisstart.htm, and typed localhost/statictest.htm, I got the permissions error.
So since one of the files was working and one wasn't, I decided to compare their permissions. (You do this using the File Explorer. Right click on the file, click on Properties, click on Security Tab. To make changes, click on Edit.) I saw that the successful one had a user listed that the unsuccessful one did not. So I added a user for the statictest.htm file to the permissions list with full control. That solved the issue for that file and it displayed normally.
I now am back to getting a blank page when I type in localhost. It must not be a permissions issue, because otherwise I'd get the permissions error page. I'm not sure what the cause of the blank page is. But as long as I can get files to display when I give their name, I am happy enough.
I am happy to report that my PHP installation is also working, at least as judged by the fact that the phpinfo() function displays properly.
So to sum up: if you are having problems getting IIS to work on Windows 8.1, try adding more IIS modules and make sure your permissions are in order. I think the most important ones to add are Static Content and HTTP Errors. Also, of course, CGI if you are going to use PHP.
I know this is an older post, but in case anyone, like me, already had "static content" enabled, there was one other thing that needed to be done to resolve this issue.
Under "Programs and Features" -> "Turn Windows features on or off"
Expand "Internet Information Services" -> "World Wide Web Services" -> "Application Development Features"
Make sure that "ASP.NET 4.5" (and if needed/installed 3.5) are selected. This should automatically check ".Net Extensibility" for the selected version, and it should also enable ISAPI filters and Extensions.
By default (for me at least) these options were not turned on when I enabled IIS. I was getting a 500 error in IE if I had "Show Friendly Error Messages" turned on in IE, but if I turned that option off, I would get a completely blank page.
For me, the reason was that I had two different HTTP handlers in the config with the same name. I didn't get any errors, just blank response.
I'm guessing that some other parts of the configuration may result in a similar behavior. Try commenting out some parts of Web.config file in case you cannot figure the problem out.
Same issue.
Win 10 upgraded from 7. Default documents server blank and without error.
Static Content and Default Document features already enabled.
I resolved by disabling both features, rebooted and tried(received error 404), enabled both features, rebooted, pages served properly.
For me, I was using Windows Server 2008 on an Azure machine, it was missing some packages which can be installed using "Web Platform Installer", and then search for "recommended server configuration for web hosting providers"
I encountered the blank page problem as well on IIS 8.5 on Windows Server 2012 R2.
I had StaticContent installed as Windows feature.
What finally fixed it for me was changing the Path Type of the StaticFile Handler under [IIS Manager -> Server on left pane -> Handler Mappings -> StaticFile] from "Unspecified" to "File or Folder".
You can also change this on a per web site basis instead of the entire server (but I don't really see a reason why to do so, as it breaks pretty much any page). Make sure, however, that the site does not have an overriding setting for the StaticFile handler, as the site scoped one is preferred over the global one.
I have installed MOSS 2007 on Windows Server 2008.
I am facing a strange problem:
I am unable to logon to SharePoint using IE 8, but am able to using Firefox. Pl note that I have taken care of the security in IE.
After creating a web application, when I try to chage the web application for creating a Site collection..I am unable to change it (even if I select the web application it says "No Selection".
I am unable to add web parts to any of the sites created! ( Pl note that I have created the sites by using a workaround..changing the SiteId=null to site Id = Id of the Site using SharePoint Manager)
I find no entries in the logs or no error messages..
Please help me in this regard.
Grace
IE8 on Windows Server 2008 is much more stringent with its default security settings. Even disabling IE Enhanced Security Configuration does not allow all functionality. This is to discourage you from logging into the server and perhaps inadvertantly installing an IE addon that compromises security.
You really should connect to SharePoint Central Administration from your local machine. Then you won't have the security problems and also will be following Microsoft best practice.
Try adding the Site (Central Admin ) to the Trusted Site in IE and Make the Security Setting as Low. It will give all the Required stuffs like Javascript and it should solve your issue.
I have also had the same problem, not being able to select a web application. In our case we ended up reinstalling sharepoint (actually a clean install of the OS), then it worked fine.
There was probably some step in the installation that we did not do in the correct order.
Installing Sharepoint on Windows Server 2008 is not a regular install. Make sure you have the latest Cumulative update installed + SP2. Better yet, slipstream the installation.
Take note, especially when installing Language Packs attention is need when performing the install, there is a specific order in which to install the product / updates / packs.
More info Code eater blog post
You may need to disable the loop back checking if the site is using a host header name. See this article for more details.
can someone please tell me what i need so that i can see the explorer view for a library in sharepoint? it works on one machine and not another. it sometimes works on a vista client but not xp. it works in internet explorer but does not work on another machine with the same settings.
please help. wss 3.0 on windows server 2008 with vista and xp clients.
Thanks
It requires WebDav to be enabled on the server part, and WebClient to be running at the client. WebClient is just a service, see this technet entry for specific information on how to start it.
If WebClient is already running, make sure the SharePoint site is added to the "Trusted Sites" in IE. In Vista SP1 and up, the WebClient has a private list of "Trusted Sites" in the registry.
SharePoint explorer view actually doesn't work in IE8 on Windows XP SP3. The issue only occurs if your using SSL, and I've not seen a good solution to make this work. Interestingly, it works fine in IE7. Now if your using any other web browser besides IE, there is no way to get explorer view to work currently.
Also, the 64bit version of IE is a Level 2 browser with SharePoint 2007, so certain features don't work on that either. I think the explorer view is one of them, but my memory could be wrong. Microsoft has published what currently does and does not work between different browsers on SharePoint.
Make sure you have a site collection located at your web application root. This solved the problem in my case.
Problem : explorer view not working properly, except when :
explorer view selected in a subfolder of the document library
a network favorite pointing to the document library was created
I was trying to do a quick backup of a bunch of files, and the explorer view was not working. What finally worked was mapping a network drive to the sharepoint server, and then I was able to bulk copy and paste the folders/files to my backup server.
I don't know why MS makes so many things really difficult. But they do. But that worked for me.