November 23, 2010 at 12:21 pm
[font="Verdana"]Hi,
While connecting to Report Server we are getting "Internet Explorer cannot display the webpage" error / message which is intermittent, attached herewith as well. The next moment we try the same URL, it connects to the report server.
Even the error / message returned by explorer are self explanatory that:
1. There might be a problem with internet connection or
2. Website might be encountering problem or
3. Typing error in address bar.
However we are not agree with the 1st and 3rd option. Because the next moment we try the same URL the report folder appears. So here I wanted to know in detail on the 2nd option. What kind of website problem may occur? We have checked the report server logs / trace files; however we did not found any exceptional information there. Simultaneously we have been through the below URL as well: http://msdn.microsoft.com/en-us/ms156468.aspx. Even here no such information we did get.
Thanks in advance,
-- Mahesh Bote
[/font]
MH-09-AM-8694
November 30, 2010 at 12:31 am
Hard to tell being I'm not there with ya. But have you looked at the SSRS logs to see if you are getting any messages that might give a clue to your situation? Wouldn't hurt to look at the Events View in Administrative Tools at the logs. To see if there's any errors being thrown when the problem does occur. Look in the Application log. See if there are any messages saying something about the SSRS service not able to connect to ReportServer. Look in the Security log. See if there are any Failure Audits and what for. I've even gone as far as looking at the IIS logs. See if there are any 401.1, 401.2. This might go hand in hand with the Failure Audits in the Security log. If you are in a domain sometimes you could be having intermittent Active Directory issues causing authentic ion to fail. Just a thought but something to check and rule out.
Wouldn't hurt to try to ping the Reporting Service URL and IP, also do try tracert to the IP and/or Reporting Service URL. To discount network issues.
Might need some more info on your setup to help more. Like what version of SSRS is it? Is it a standalone server or web farmed? Is it the only application running on the server or are there other web sites, applications on the server? For example, does it share the same server as SQL Server or is SQL on another server?
See you might be getting intermittent results because there might be a problem of getting response from SQL server. It has to query the RS catalog to get data, resources, etc ... in order to build the Report Manger.
Another thing to think about is how heavy is you SQL Server being used that has the RS catalogs on them. For example: If you have SQL Server on a single server as well as Analysis Services on there also while someone is loading/processing a cube. Could be running out of memory and resources which cause SSRS to lag/fail in response.
Things you could try is recycle IIS. If that doesn't help there's the old tried and true solution to windows -- reboot the server. How long has it been since the last time the server has been rebooted? Disk clean? Drives defragged? Not saying this will fix it, but if it’s been awhile it wouldn't hurt. Not sure the extent of your authority or permissions. Guess that all depends on some of the questions above, like is it a standalone service or is it shared.
If you have SSRS in a web farmed solution you could shut down services on one server and test the issue to see if it's related to one particular server. If standalone, have you tried to hit it the Report Manger on the server to see if you get the same results? Otherwise, does this problem occur from client/user workstation only?
Have you ever used SQL Profiler before? Might have to do a test with someone hitting SSRS Web Report Manger while you or someone runs SQL Profiler to see if by chance that your SQL Server isn’t' responding from time to time. You would connect to your SQL Server that host the RS Catalogs and see if you don't get a request from SSRS and a response from SQL Server. The case you do is run one when it works and save it. Run one again until you get a failure and save it. See if you can see a difference.
I've ran out of suggestions to make as a way to trouble shoot the issue for now.
December 2, 2010 at 10:39 am
IN IE, the default behavior is to hide the true error. You'll get better information if you go to "internet options" in the tools menu, click on the advanced tab, and uncheck "show friendly HTTP error messages."
There is a similar setting for IIS (You posted under 2005, so I think you're using IIS). You can enable detailed error messages from "Computer Management" (on the server), select "Internet Information Services (IIS) Manager" under "Services" in the left tree view.
In IIS 7, the following will work: select the ssrs site in the rmiddle tree view, open "Error Pages" from the right pane, select "Edit Features" from the right-hand list, and ensure that "detailed errors" is selected.
I don't remember how to do this from earlier versions of IIS (it's easier though) but the features are named roughly the same, so with a bit of searching or googling you should be able to find it.
Dan Guzman - Not the MVP (7/22/2010)
All questions have to be prefaced by Server version and 'according to MS Docs' or 'my own personal opinion based on how much detail I felt like digging into at the time.'
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply